first-principles-think…
Systematic first principles thinking for any problem domain. Use when the user says "analyze from first principles", "第一性原理", "从根本分析", "从零开始思考", "think from…
Guide for contributing to Trellis documentation and marketplace. Covers adding spec templates, marketplace skills, documentation pages, and submitting PRs across both the Trellis main repo and docs repo. Use when someone wants to add a new spec template, add a new skill to the
$ npx -y skills add mindfold-ai/trellis --skill contribute --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/contributeContext preview
The summary Claude sees to decide when to auto-load this skill.
Guide for contributing to Trellis documentation and marketplace. Covers adding spec templates, marketplace skills, documentation pages, and submitting PRs across both the Trellis main repo and docs repo. Use when someone wants to add a new spec template, add a new skill to the
name: contribute description: "Guide for contributing to Trellis documentation and marketplace. Covers adding spec templates, marketplace skills, documentation pages, and submitting PRs across both the Trellis main repo and docs repo. Use when someone wants to add a new spec template, add a new skill to the marketplace, add or update documentation pages, or submit a PR to this project."
Contributions are split across two repos:
| What | Repo | Purpose | |------|------|---------| | Documentation pages | [mindfold-ai/docs](https://github.com/mindfold-ai/docs) | Mintlify doc site | | Skills + Spec templates | [mindfold-ai/Trellis](https://github.com/mindfold-ai/Trellis) | `marketplace/` directory |
docs/ ├── docs.json # Navigation config (MUST update for new pages) │ ├── index.mdx # English homepage ├── quickstart.mdx # English quickstart ├── zh/index.mdx # Chinese homepage ├── zh/quickstart.mdx # Chinese quickstart │ ├── guides/ # English guide pages ├── zh/guides/ # Chinese guide pages │ ├── templates/ # English template pages ├── zh/templates/ # Chinese template pages │ ├── skills-market/ # English skill marketplace pages ├── zh/skills-market/ # Chinese skill marketplace pages │ ├── blog/ # English tech blog ├── zh/blog/ # Chinese tech blog │ ├── changelog/ # English changelog ├── zh/changelog/ # Chinese changelog │ ├── contribute/ # English contribution guide ├── zh/contribute/ # Chinese contribution guide │ ├── showcase/ # English showcase └── zh/showcase/ # Chinese showcase
marketplace/
├── index.json # Template registry (lists all available templates)
├── README.md # Marketplace overview
├── specs/ # Spec templates
│ └── electron-fullstack/
│ ├── README.md
│ ├── frontend/
│ ├── backend/
│ ├── guides/
│ └── shared/
└── skills/ # Skills
└── trellis-meta/
├── SKILL.md
└── references/The navigation uses a **language-based structure**:
{
"navigation": {
"languages": [
{
"language": "en",
"groups": [
{
"group": "Getting started",
"pages": ["index", "quickstart"]
},
{
"group": "Guides",
"pages": ["guides/specs", "guides/tasks", ...]
},
{
"group": "Resource Marketplace",
"pages": [
{
"group": "Skills",
"expanded": false,
"pages": ["skills-market/index", "skills-market/trellis-meta"]
},
{
"group": "Spec Templates",
"expanded": false,
"pages": ["templates/specs-index", "templates/specs-electron"]
}
]
}
]
},
{
"language": "zh",
"groups": [
// Same structure with zh/ prefix
]
}
]
}
}**Key points**:
Spec templates live in the **Trellis main repo** at `marketplace/specs/`.
marketplace/specs/your-template-name/
├── README.md # Template overview (required)
├── frontend/ # Frontend guidelines
│ ├── index.md
│ └── ...
├── backend/ # Backend guidelines
│ ├── index.md
│ └── ...
├── guides/ # Thinking guides
│ └── ...
└── shared/ # Cross-cutting concerns (optional)
└── ...Structure varies by stack. Include directories relevant to your template.
Add your template to `marketplace/index.json` in the Trellis repo:
{
"id": "your-template-id",
"type": "spec",
"name": "Your Template Name",
"description": "Brief description of the template",
"path": "marketplace/specs/your-template-name",
"tags": ["relevant", "tags"]
}**English**: `templates/specs-your-template.mdx` **Chinese**: `zh/templates/specs-your-template.mdx`
Use this frontmatter:
--- title: 'Your Template Name' description: 'Brief description' ---
Find the `Spec Templates` nested group and add your page:
{
"group": "Spec Templates",
"expanded": false,
"pages": ["templates/specs-index", "templates/specs-electron", "templates/specs-your-template"]
}Do the same for Chinese under `"language": "zh"`:
{
"group": "Spec Templates",
"expanded": false,
"pages": [
"zh/templates/specs-index",
"zh/templates/specs-electron",
"zh/templates/specs-your-template"
]
}Add your template to the table in:
Skills live in the **Trellis main repo** at `marketplace/skills/`.
marketplace/skills/your-skill/ ├── SKILL.md # Skill definition (required) └── references/ # Reference docs (optional)
See [Claude Code Skills documentation](https://code.claude.com/docs/en/skills) for SKILL.md format.
Add your skill to `marketplace/index.json` in the Trellis repo:
{
"id": "your-skill-id",
"type": "skill",
"name": "Your Skill Name",
"description": "Brief description",
"path": "marketplace/Repo: mindfold-ai/trellis
Systematic first principles thinking for any problem domain. Use when the user says "analyze from first principles", "第一性原理", "从根本分析", "从零开始思考", "think from…
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos.…
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: \"Why is X failing?\", \"Where does this error come from?\",…
Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: \"How…
Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples:…
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: \"Is it safe to change X?\",…