before-dev

Load package specs and shared guides before coding tasks.

4|1|Updated Aug 9, 2025
One-click install
npx skills add https://github.com/LinnkidChen/Stock-Tracker --skill before-dev-linnkidchen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: before-dev
Source: https://github.com/LinnkidChen/Stock-Tracker/tree/main/.agents/skills/before-dev
Command: npx skills add https://github.com/LinnkidChen/Stock-Tracker --skill before-dev-linnkidchen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discovers and applies project-specific coding guidelines before implementation begins to ensure consistent standards.

Core Features & Use Cases

  • Discover and load package-spec context to ensure adherence to conventions across different modules (e.g., cli/ and docs-site/).
  • Read Pre-Development Checklists and shared guides to inform planning and task scoping before writing code.
  • Enforce consistent coding standards by referencing central guidelines and avoiding drift when switching packages.

Quick Start

Run the pre-development onboarding flow to load all package specs and shared guidelines before starting any coding task.

Frequently Asked Questions about before-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce coding standards before starting development across multiple packages?

Pre-development checklists enforce baseline conventions by loading package-specific spec indexes and shared guides before coding begins. They prevent standard drift when switching packages or starting fresh tasks across different modules.

What is the best way to prevent coding standard drift when switching between project packages?

Preventing coding standard drift when switching packages requires discovering and loading package-specific spec contexts before implementation. Referencing central guidelines and shared guides maintains consistent conventions across different modules.

How do I load project-specific coding guidelines for a new development task?

You can load project-specific coding guidelines by running a pre-development onboarding flow. This process reads pre-development checklists, consults shared guides, and loads spec indexes to inform planning and task scoping before writing code.

Do I need to load spec indexes before writing code in a new package context?

Yes, you need to load spec indexes before writing code in a new package context to ensure baseline conventions are met. Loading these specs applies project-specific coding guidelines and enforces consistent standards across different modules.

When should I use a pre-development onboarding flow for coding standards?

You should use a pre-development onboarding flow when starting a fresh task, switching packages, or working across multiple contexts like cli/ and docs-site/. It aligns project standards and enforces baseline conventions before implementation begins.