SkillCurated by metahubEval warnings

trellis-before-dev

Name: trellis-before-dev
Author: huangjunsen0406

Discovers and injects project-specific coding guidelines from .trellis/spec/ before implementation begins. Reads spec indexes, pre-development checklists, and shared thinking guides for the target package. Use when starting a new coding task, before writing any code, switching to a different package, or needing to refresh project conventions and standards.

pinned to #f0ff8e5updated 2 weeks ago

6/11Verified publisherCurated by MetaHubActively maintainedLicensedDocumentedClean repo

Ask your AI client: “install skills/trellis-before-dev”.

Requires the metahub MCP server installed in your client. Set up MCP.

mh install skills/trellis-before-dev

metahub onboarded this repo on the author's behalf.

If you own github.com/huangjunsen0406/py-xiaozhi on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.

Claim this repo

Stars

3,396

Last commit

2 weeks ago

f0ff8e5

Latest release

published

2 weeks ago

#cross-platform
#edge-computing
#embodied-ai
#esp32
#esp32-s3
#iot
#mcp
#mcp-client
#mcp-server
#multi-modal
#python
#raspberry-pi
#robotics
#voice-assistant
#xiaozhi-esp32

About this skill

Pulled from SKILL.md at publish time.

Read the relevant development guidelines before starting your task.

Evaluation report

Warnings

Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.f0ff8e5· 2 weeks ago

Kind-specific

Skill: SKILL.md present
found at .claude/skills/trellis-before-dev/SKILL.md · frontmatter source: SKILL.md
Skill: body content present
154 words · 1,168 chars
Skill: triggers declaredwarn
No `trigger` phrases in SKILL.md frontmatter
Add `trigger:` lines so Claude knows when to activate this skill — e.g. `when building MCP servers` or `for diagram creation`.
Skill: allowed-tools scope
no allowed-tools restriction (Claude may use anything)

Release history

releasecurrentf0ff8e5warn2 weeks ago

View on GitHub

Read the relevant development guidelines before starting your task.

Execute these steps:

Discover packages and their spec layers:

python3 ./.trellis/scripts/get_context.py --mode packages

Identify which specs apply to your task based on:
- Which package you're modifying (e.g., cli/, docs-site/)
- What type of work (backend, frontend, unit-test, docs, etc.)
Read the spec index for each relevant module:
```
cat .trellis/spec/<package>/<layer>/index.md
```
Follow the "Pre-Development Checklist" section in the index.
Read the specific guideline files listed in the Pre-Development Checklist that are relevant to your task. The index is NOT the goal — it points you to the actual guideline files (e.g., error-handling.md, conventions.md, mock-strategies.md). Read those files to understand the coding standards and patterns.
Always read shared guides:
```
cat .trellis/spec/guides/index.md
```
Understand the coding standards and patterns you need to follow, then proceed with your development plan.