trellis-bootstrap
Configures the boilerplate required to integrate Trellis AI into existing development projects.
Install
mkdir -p .claude/skills/trellis-bootstrap && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5908" && unzip -o skill.zip -d .claude/skills/trellis-bootstrap && rm skill.zipInstalls to .claude/skills/trellis-bootstrap
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Initialize Trellis AI workflow system in a project. Use when user mentions "Trellis", "初始化 Trellis", "setup Trellis", "install Trellis", or wants to add AI-assisted development workflow to their project. This is a one-time setup skill.Key capabilities
- →Initialize Trellis AI workflow
- →Configure project structure guidelines
- →Enable session history tracking
- →Setup slash command automation
How it works
The skill installs the Trellis CLI and runs an initialization command to create project-specific configuration directories and automation hooks.
Inputs & outputs
When to use trellis-bootstrap
- →Initialize Trellis in new repository
- →Setup Trellis AI workflow
- →Add Trellis AI to project
About this skill
Trellis Bootstrap
One-time setup for Trellis - the AI workflow system that helps your AI assistant remember project context across sessions.
What is Trellis?
Trellis provides:
- Structure - Store coding guidelines in
.trellis/structure/that AI follows - Memory - Track session history in
.trellis/agent-traces/ - Automation - Slash commands like
/start,/parallel,/finish-work
Prerequisites Check
Before starting, verify:
# Check Node.js (required: v18+)
node --version
# Check npm
npm --version
If Node.js is not installed, ask the user to install it first.
Installation Steps
Step 1: Install Trellis CLI
npm install -g @mindfoldhq/trellis@latest
Verify installation:
trellis --version
Step 2: Get Developer Name
Ask the user for their name/username. This will be used for tracking their sessions.
Example question: "What name should I use for your developer profile? (e.g., your GitHub username)"
Step 3: Initialize in Project
Run in the project root:
trellis init -u <developer-name>
This creates:
.trellis/
├── workflow.md # Start here
├── structure/ # Development guidelines
│ ├── frontend/
│ └── backend/
├── agent-traces/<name>/ # Your session history
└── scripts/ # Automation scripts
.claude/
├── commands/ # 13 slash commands
├── agents/ # 6 agent definitions
└── hooks/ # Automation hooks
.cursor/
└── commands/ # 12 slash commands
AGENTS.md # AI reads this first
Step 4: Verify Setup
# Check created files
ls -la .trellis/
ls -la .claude/commands/
Post-Setup Instructions
Tell the user:
- Start using Trellis - Run
/startat the beginning of each session - Add guidelines - Edit files in
.trellis/structure/to customize AI behavior - Track progress - Run
/record-agent-flowat the end of sessions
Quick Reference
| Command | When to Use |
|---|---|
/start | Beginning of every session |
/parallel | Complex features (multi-agent pipeline) |
/before-frontend-dev | Before frontend coding |
/before-backend-dev | Before backend coding |
/finish-work | Before committing |
/record-agent-flow | End of session |
Success Criteria
Setup is complete when:
-
trellis --versionshows version number -
.trellis/directory exists withworkflow.md -
.claude/commands/contains slash command files -
AGENTS.mdexists in project root
After successful setup, this skill is no longer needed. The user should use /start to begin working with Trellis.
Note: This is a bootstrap skill. Once Trellis is initialized, use the built-in /start command instead of this skill.
When not to use it
- →When Trellis is already initialized
- →For non-AI assisted development projects
Prerequisites
Limitations
- →Requires manual verification of created files
- →One-time setup only
How it compares
This automates the setup of multiple configuration files and directory structures that would otherwise require manual creation and organization.
Compared to similar skills
trellis-bootstrap side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| trellis-bootstrap (this skill) | 1 | 3mo | Review | Beginner |
| opencode-cli | 14 | 7mo | Review | Advanced |
| claude-automation-recommender | 47 | 2mo | Review | Beginner |
| mcp-integration | 21 | 8mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by mindfold-ai
View all by mindfold-ai →You might also like
opencode-cli
SpillwaveSolutions
This skill should be used when configuring or using the OpenCode CLI for headless LLM automation. Use when the user asks to "configure opencode", "use opencode cli", "set up opencode", "opencode run command", "opencode model selection", "opencode providers", "opencode vertex ai", "opencode mcp servers", "opencode ollama", "opencode local models", "opencode deepseek", "opencode kimi", "opencode mistral", "fallback cli tool", or "headless llm cli". Covers command syntax, provider configuration, Vertex AI setup, MCP servers, local models, cloud providers, and subprocess integration patterns.
claude-automation-recommender
anthropics
Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.
mcp-integration
anthropics
This skill should be used when the user asks to "add MCP server", "integrate MCP", "configure MCP in plugin", "use .mcp.json", "set up Model Context Protocol", "connect external service", mentions "${CLAUDE_PLUGIN_ROOT} with MCP", or discusses MCP server types (SSE, stdio, HTTP, WebSocket). Provides comprehensive guidance for integrating Model Context Protocol servers into Claude Code plugins for external tool and service integration.
hook-development
anthropics
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.
agent-factory
alirezarezvani
Claude Code agent generation system that creates custom agents and sub-agents with enhanced YAML frontmatter, tool access patterns, and MCP integration support following proven production patterns
swarm-advanced
ruvnet
Advanced swarm orchestration patterns for research, development, testing, and complex distributed workflows