trellis-before-dev

To inject coding guidelines before implementation, this Skill discovers and reads project-specific standards from the .trellis/spec directory, reading the index and guideline files like error-handling.md to establish context before you start coding.

Applying coding standards across packages is handled by discovering relevant spec layers based on the target package and task type, then consulting shared guides and the Pre-Development Checklist to ensure consistent conventions.

You need to refresh project conventions when switching packages or starting new coding tasks, ensuring that the correct backend, frontend, docs, or tests guidelines are injected into your current workflow context.

Pre-development context discovery works by identifying the target package and task type, reading the spec index and individual guideline files, and applying those shared guides to establish coding standards before implementation begins.

Yes, a .trellis/spec directory is required because the Skill reads the Pre-Development Checklist, index, and individual guideline files such as conventions.md from that location to inject the correct standards.

Yes, you can use this for frontend and backend standards separately because it identifies relevant specs based on the target package and task type, applying the correct guidelines to your specific workflow.