Instructions for PackmindHub/packmind: This standard defines the recommended data flow pattern for frontend routes in the Packmind codebase using React Router v7 in framework mode with TanStack Query for data management. It ensures consist... .
Instructions for PackmindHub/packmind: A global error boundary is already configured at the root level (in root.tsx) that automatically catches all page crashes, 404s, and loader failures. This standard defines when and how to use explicit... .
Instructions for PackmindHub/packmind: This codebase uses React Router v7 with organization and space scoping in URLs (e.g., /org/{orgSlug}/space/{spaceSlug}/recipes). To maintain consistency, improve maintainability, and simplify navigati... .
Instructions for PackmindHub/packmind: TanStack Query uses prefix matching to invalidate cached queries, matching keys from left to right like a file path. Properly structured query keys enable efficient cache invalidation at any scope lev... .
This standard provides guidelines for writing SQL queries using TypeORM in back-end repositories located in /infra/repositories/\Repository.ts. TypeORM offers multiple approaches to query data, but f... .
This standard establishes clean code practices in TypeScript for back-end development to enhance maintainability and ensure consistent patterns across services. It covers logging best practices, error... .
Domain events enable communication between hexas without creating direct dependencies. Apply these rules when creating events, emitting them, or implementing listeners to react to events from other do... .
This standard defines how domain packages communicate with each other through the Port/Adapter pattern in our DDD monorepo architecture. By following these rules, you prevent circular dependencies, ma... .
Enforce data isolation and consistent query patterns in repositories extending SpaceScopedRepository or OrganizationScopedRepository, ensuring tenant-safe data access across the Packmind codebase. .
This standard defines how to structure use cases in the Packmind monorepo following hexagonal architecture principles. Use cases represent the entry points to domain logic and must follow consistent p... .
Instructions for PackmindHub/packmind: This standard provides guidelines for writing SQL queries using TypeORM in back-end repositories located in /infra/repositories/\Repository.ts. TypeORM offers multiple approaches to query data, but f... .
Instructions for PackmindHub/packmind: This standard establishes clean code practices in TypeScript for back-end development to enhance maintainability and ensure consistent patterns across services. It covers logging best practices, error... .
Instructions for PackmindHub/context-evaluator, covering claude.md, development workflow, after every code modification, pre-commit hook and common commands.
Add a new property to the AI agents database. Use when the user wants to add, create, or introduce a new column, property, field, or feature to track across all agents in the comparison matrix. Handles all four required steps - database updates, groups.json, table display, and GitHub issue templates.
Scaffold a new Drizzle-backed repository by defining a domain port, implementing it with typed Drizzle queries, and wiring it into DI to provide consistent, testable persistence whenever a use case needs read/write access to a new or refactored table.
Scaffold a hexagonal, framework-agnostic application use case as a pure deps+input function with a colocated bun:test using makeDeps so business operations stay easily testable and cleanly separated from HTTP concerns when adding or refactoring backend application logic.
Run the full local pre-PR quality gate (frozen-lockfile install, lint, typecheck, tests, build, and optional Docker build) to catch CI and type errors early and ensure your pull request against main passes on the first try.
How to safely add, edit, and verify Drizzle migrations in the skills-observability backend (PostgreSQL + Drizzle ORM). Covers the schema-first generation flow, the strict monotonicity invariant of journal.json when timestamps (whose violation has silently skipped migrations in production), idempotent SQL patterns, and…
Complete automated onboarding: analyzes codebase, creates package, and generates standards & commands via CLI. Automatic package creation when none exist, user selection when packages are available.
Use when updating, adding, fixing, changing, or deprecating Packmind playbook artifacts (standards, commands, skills). Triggers on explicit phrases like "update packmind standard", "add a packmind skill", "fix packmind command", "change packmind playbook", "deprecate a standard". Also triggers — even without an…
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.