Skip to content

Latest commit

 

History

History
54 lines (35 loc) · 3.07 KB

AGENTS.md

File metadata and controls

54 lines (35 loc) · 3.07 KB

[Skills Index]|roots: .claude/skills,.codex/skills,.opencode/skills,.gemini/skills,.goose/skills |IMPORTANT: Prefer retrieval-led reasoning over pre-training-led reasoning for any skill tasks. |spec-test-driven-development:{SKILL.md} |specifying-requirements:{SKILL.md} |acceptance-test:{SKILL.md} |test-driven-development:{SKILL.md,PYTHON.md,RUST.md} |refactoring-code:{SKILL.md,FILE-ORGANIZATION.md,RUST.md} |write-commit-message:{SKILL.md} |install-dependencies:{SKILL.md,PYTHON.md,RUST.md,TYPESCRIPT.md} |update-dependencies:{SKILL.md,PYTHON.md} |evaluation:{SKILL.md} |create-skill:{SKILL.md} |pre-commit-hooks:{SKILL.md}

🚨 CRITICAL PRE-FLIGHT CHECK 🚨

BEFORE writing ANY code, making ANY edits, or implementing ANYTHING:

  1. STOP - Do not proceed directly to implementation
  2. CHECK - Review the Skills Index above
  3. MATCH - Identify if ANY skill applies to the user's request
  4. INVOKE - Use the Skill tool FIRST (this is MANDATORY, not optional)

NO EXCEPTIONS: Even with detailed plans, even with clear instructions, ALWAYS check and use skills first.

Overview

This repository contains reusable skills for software development workflows using specification-driven and test-driven development practices.

Skills

Development workflow skills are available to guide common tasks:

  • spec-test-driven-development: Use when implementing new features or functionality. Provides complete workflow from specification through testing to implementation.

  • specifying-requirements: Use when writing or updating spec.yaml files. Defines requirement format and user story structure.

  • acceptance-test: Use when writing acceptance tests or adding scenarios to spec.yaml. Defines Given/When/Then format and acceptance test patterns.

  • test-driven-development: Use when writing tests or implementing code. Defines RED-GREEN-REFACTOR cycle and test execution workflow. Includes language-specific guidance in PYTHON.md, RUST.md files.

  • refactoring-code: Use during REFACTOR phase of TDD (after GREEN), when logic is duplicated, or when locality of behavior is violated. Defines search-first workflow, duplication detection, locality principles, and safe refactoring practices.

  • write-commit-message: Use when creating git commits. Defines conventional commit format and message structure guidelines.

  • install-dependencies: Use when adding project dependencies. Defines dependency management rules and language-specific patterns for Python, Rust, and TypeScript.

  • update-dependencies: Use when updating existing pinned dependencies. Defines unpin-resolve-repin workflow with test verification and rollback on failure.

  • evaluation: Use when creating or updating agent evaluation suites. Defines eval structure, rubrics, and validation patterns.

  • create-skill: Use when creating or modifying skills. Defines skill file structure, naming conventions, and integration patterns.

  • pre-commit-hooks: Use when running pre-commit hooks manually. This project uses prek, not pre-commit. Defines correct commands for running hooks.