Discover and inject project-specific coding guidelines into a development workflow.
npx skills add https://github.com/MaplumeX/deepresearch --skill before-dev-maplumex
Please help me install this Agent Skill. Skill: before-dev Source: https://github.com/MaplumeX/deepresearch/tree/main/.agents/skills/before-dev Command: npx skills add https://github.com/MaplumeX/deepresearch --skill before-dev-maplumex
New coding tasks often proceed without consulting project-specific rules, causing inconsistent implementations, missed checklists, and avoidable rework. This Skill ensures developers read the appropriate spec layers and shared guides before writing any code to reduce integration issues and maintain repository conventions.
Run the before-dev steps to find and read the package spec index, the listed guideline files, and the shared guides before you begin coding.
High-intent search queries and answers about installing and using this skill.
To load project coding guidelines before development, discover package-level spec indexes by reading .trellis/spec files and referenced guideline documents, ensuring pre-development checklists are followed prior to writing code.
Pre-development checklists in repository spec index files are entries that reference guideline documents such as error handling, conventions, and mock strategies, ensuring developers review required rules before starting a new coding task.
To enforce code conventions when switching packages, run discovery steps to locate the package-level spec index, read the referenced guideline files, and confirm your implementation plan aligns with documented repository conventions.
Yes, you need to read shared guides before starting cross-cutting or unfamiliar development tasks to ensure team-wide guidance is reviewed, reducing integration issues and maintaining repository conventions across the project.
The best way to onboard developers to repository coding conventions is to locate spec index files, read referenced guideline documents, and verify pre-development checklists are completed before any package-level code modifications begin.
Yes, you can use this pre-development spec discovery for backend package modifications by running the discovery steps, reading the package index and referenced guidelines, and confirming the implementation plan follows documented conventions.
LonelyHerbivoreLoads .trellis/spec development guidelines and checklists before coding tasks.
yuanjing-hashDiscover spec layers and provide pre-coding guidelines for software projects.
SDDKKKDiscover and inject project-specific coding guidelines from .trellis/spec indexes.
BaSui01Discover and inject .trellis/spec coding guidelines into developer context.
