ngvoicu
6 verified skills36 total stars
specmint-core
Persistent spec management for AI coding workflows. Use this skill when the user explicitly mentions specs, forging, or structured planning: says "forge", "forge a spec", "write a spec for X", "create a spec", "plan X as a spec", "resume", "what was I working on", "spec list/status/pause/switch/activate", "implement the spec", "implement phase N", "implement all phases", "generate openapi", or exits plan mode (offer to save as a spec). Also trigger when a `.specs/` directory exists at session start. Do NOT trigger on general feature requests, coding tasks, or questions that don't mention specs or forging — those are normal coding tasks, not spec management.
development8
specmint-core
Persistent spec management for AI coding workflows. Use this skill when the user explicitly mentions specs, forging, or structured planning: says "forge", "forge a spec", "write a spec for X", "create a spec", "plan X as a spec", "resume", "what was I working on", "spec list/status/pause/switch/activate", "implement the spec", "implement phase N", "implement all phases", "generate openapi", or exits plan mode (offer to save as a spec). Also trigger when a `.specs/` directory exists at session start. Do NOT trigger on general feature requests, coding tasks, or questions that don't mention specs or forging — those are normal coding tasks, not spec management.
development8
specmint-core
Persistent spec management for AI coding workflows. Use this skill when the user explicitly mentions specs, forging, or structured planning: says "forge", "forge a spec", "write a spec for X", "create a spec", "plan X as a spec", "resume", "what was I working on", "spec list/status/pause/switch/activate", "implement the spec", "implement phase N", "implement all phases", "generate openapi", or exits plan mode (offer to save as a spec). Also trigger when a `.specs/` directory exists at session start. Do NOT trigger on general feature requests, coding tasks, or questions that don't mention specs or forging — those are normal coding tasks, not spec management.
development8
specmint-core
Persistent spec management for AI coding workflows. Use this skill when the user explicitly mentions specs, forging, or structured planning: says "forge", "forge a spec", "write a spec for X", "create a spec", "plan X as a spec", "resume", "what was I working on", "spec list/status/pause/switch/activate", "implement the spec", "implement phase N", "implement all phases", "generate openapi", or exits plan mode (offer to save as a spec). Also trigger when a `.specs/` directory exists at session start. Do NOT trigger on general feature requests, coding tasks, or questions that don't mention specs or forging — those are normal coding tasks, not spec management.
development8
datasmith-pg
SQL database architect for PostgreSQL-first systems. Designs production-grade schemas from scratch, reviews and optimizes existing schemas, writes complex SQL (JOINs, CTEs, window functions), writes Flyway migrations, and advises on normalization (1NF through BCNF), indexing, and multi-tenancy. Use this skill when the user asks to model a business domain, create/review tables and constraints, troubleshoot foreign keys or query performance, write or audit SQL migrations, discuss Prisma schema, or compare SQL dialect behavior. Also trigger when a user provides existing SQL for anti-pattern or migration-safety review. Default to explicit constraint naming, timezone-safe timestamps, and evolution-safe migration guidance.
testing2
datasmith-pg
SQL database architect for PostgreSQL-first systems. Designs production-grade schemas from scratch, reviews and optimizes existing schemas, writes complex SQL (JOINs, CTEs, window functions), writes Flyway migrations, and advises on normalization (1NF through BCNF), indexing, and multi-tenancy. Use this skill when the user asks to model a business domain, create/review tables and constraints, troubleshoot foreign keys or query performance, write or audit SQL migrations, discuss Prisma schema, or compare SQL dialect behavior. Also trigger when a user provides existing SQL for anti-pattern or migration-safety review. Default to explicit constraint naming, timezone-safe timestamps, and evolution-safe migration guidance.
testing2