Before Dev
Developmentbefore-devBefore Dev is an Agent Skill for development published in the zhukunpenglinyutong/desktop-cc-gui repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
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.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/zhukunpenglinyutong/desktop-cc-gui/blob/HEAD/.agents/skills/before-dev/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/before-dev, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Read the relevant development guidelines before starting your task.
Execute these steps:
-
Read the project entry first:
cat AGENTS.md -
Discover packages and their spec layers:
python3 ./.trellis/scripts/get_context.py --mode packages -
Identify which specs apply to your task based on:
- Which implementation layer you're modifying (
frontend,backend, or repo-level docs/governance) - What type of work (backend, frontend, unit-test, docs, etc.)
- Which implementation layer you're modifying (
-
Read the spec index for each relevant module:
cat .trellis/spec/frontend/index.md cat .trellis/spec/backend/index.mdFollow 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 -
If the task changes rule entry, documentation governance, ignore policy, or host hooks, also read:
cat .trellis/spec/guides/project-instruction-layering-guide.md -
Understand the coding standards and patterns you need to follow, then proceed with your development plan.
This step is mandatory before writing any code.