The skeleton for agentic development — persistent memory, shared standards, and structured workflows for AI coding agents.
This repository also configures its own agents. See what agentskel tells them →
Cursor rule Cursor
When a single new person joins the team. Use when .memory/TEAM.md already exists and you need to append one member (with roles, optional module assignments, and optional Jira account ID) without touching the rest of the roster.
Cursor rule Cursor
When adding a new platform (subdir with its own git repo) to an existing workspace dispatcher. Runs setup-skeleton in the subdir and updates the workspace config and dispatcher AGENTS.md.
Cursor rule Cursor
Do NOT respond to any user request until you have run the session-start procedure. Read and follow .agents/skills/session-start/SKILL.md.
Cursor rule Cursor
When reading or writing to Jira tickets or Confluence pages via MCP tools. Use before any Jira transition, ticket creation, or Confluence page update to avoid common failure modes.
Cursor rule Cursor
When the user wants to think through a feature idea, explore edge cases, or produce a technical spec before implementation. Use before develop-feature to prevent mid-implementation surprises.
Cursor rule Cursor
When codebase structure has changed, MAP.md/SYMBOLS.md are missing or stale, or after major refactors and initial setup. Also run when a new module is added or files are moved between modules.
Cursor rule Cursor
When dependency versions need auditing, Last Dependency Check in CONFIG.md is overdue (14-day cadence), or before starting security-sensitive work.
Cursor rule Cursor
Checks whether this project's skeleton version is current. Surfaces the version gap and offers to run sync-skeleton. Run at the start of any session where skeleton drift might have accumulated, or on a scheduled basis.
Cursor rule Cursor
When reviewing a PR, auditing code quality, or validating changes against the project's standards and sacred behaviors.
Cursor rule Cursor
When searching for code, tracing a bug, or understanding how modules connect. Use before grepping blindly — consult the index first.
Cursor rule Cursor
When a team manages multiple platform projects sharing business logic and needs a central domain knowledge repo. Run once per organization to set up specs, parity tracking, and the knowledge bus.
Cursor rule Cursor
When the team is ready to ship a new version — version bumps, changelog finalization, dependency snapshots, and CI release trigger.
Cursor rule Cursor
When adding, renaming, or removing a field on a data model that has a mapped counterpart elsewhere — an API/DTO, a database/ORM entity, a serializer, or a cross-platform equivalent model (Android/iOS/Backend). Use whenever a model's fields change, before considering the change complete.
Cursor rule Cursor
When writing, reviewing, or running a database schema migration — adding, dropping, or altering tables, columns, indexes, or constraints — with any migration tool (Alembic, Rails, Prisma, Room, Core Data, Flyway, Liquibase, raw SQL). Use before generating a migration file, or when one appears in a diff/PR.
Cursor rule Cursor
When the user reports a bug, an error, or unexpected behavior. Enforces four structured phases — reproduction, failing test, root cause isolation, fix and verify — to stop guess-and-check loops.
Cursor rule Cursor
When the user asks to implement a new feature end-to-end requiring planning, branch creation, implementation, testing, and PR. Use for work that goes beyond a simple fix or ad-hoc task.
Cursor rule Cursor
When writing, modifying, or reviewing application code. Provides code quality standards, SOLID principles, design philosophy, and platform-specific implementation guidance.
Cursor rule Cursor
When a design discussion or evaluation is interrupted by a task or workflow, or when the user says "present the discussion," "where were we," "show me the discussion," or "resume" — save or resurface the discussion state using Session Notes.
Cursor rule Cursor
When working on features that require domain knowledge — business rules, terminology, or invariants specific to this project. [Replace this description and the content below with your project's domain.].
Cursor rule Cursor
Systematic resolution of catalogued tech debt items from TECHDEBT.md. Use when assigned a specific debt ID (AP-XXX, BUG-XXX, SI-XXX, etc.).
Cursor rule Cursor
Git branching, commit, and PR procedures. Use when creating branches, making commits, or opening pull requests. Enforces branch naming, commit message format, and PR rules.
Cursor rule Cursor
Fast-path workflow for production bugs that cannot wait for the normal release cycle. Requires explicit tech lead sign-off before branching.
Cursor rule Cursor
When the user asks to implement a specific Jira ticket (e.g. "Implement PROJ-1234"). Use when taking a ticket from backlog to merged PR, with automatic status transitions and QA handoff.
Cursor rule Cursor
Generic wrapper for any ad-hoc implementation request that doesn't match a specific workflow (develop-feature, fix-tech-debt, hotfix). Ensures pre-flight, planning, and task-completion happen for every task — not just named workflows.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: