CarlosFerOrduna
- 10 skills
- 0 followers
- 1 day ago last updated
- ▌ Commit · carlosferordunaPrepare, present, and approve Conventional Commit and push operations. Use when the user runs /commit or /push, says 'commit' or 'push', or when a checkpoint or the requirement ends and a commit message must be approved first.
- ▌ Typeorm · carlosferordunaTypeORM entity, relation, repository, query, and configuration conventions shared across engines. Load when designing entities, relations, queries, or TypeORM setup; load the matching per-engine skill alongside it.
- ▌ Database · carlosferordunaDatabase schema and migration conventions. Load when touching database schema, migrations, or ORM configuration.
- ▌ Typeorm Pg · carlosferordunaPostgres-specific TypeORM conventions - snake_case identifiers (no forced quoting), uuid primary keys, timestamptz UTC timestamps, boolean soft delete, and partial indexes. Load alongside typeorm for Postgres projects.
- ▌ Typeorm Mssql · carlosferordunaMSSQL-specific TypeORM conventions - camelCase identifiers, int identity primary keys, getutcdate timestamps, bit soft delete, and filtered unique indexes. Load alongside typeorm for SQL Server projects.
- ▌ Code Intelligence · carlosferordunaCodebase search and graph navigation - ripgrep (fast text search), ast-grep (structural patterns), and graphify (architecture graphs when graphify-out exists). Load when searching code, tracing references, understanding file relationships, or answering architecture questions; detects which tools exist and falls back to built-in search.
- ▌ Nestjs Code Style · carlosferordunaTypeScript / NestJS code style - symbol, directory, and file naming with responsibility suffixes, general code conventions, import style, type/enum/constant placement, and repository methods that express business intent. Load when writing or reviewing TypeScript / NestJS code.
- ▌ Testing Standards · carlosferordunaTesting conventions - Jest framework, unit tests alongside the code they cover, integration tests in a separate test/ directory, and ephemeral agent tests removed when the work is done. Load when writing or modifying tests.
- ▌ Commit Conventions · carlosferordunaConventional Commits with a leading gitmoji - valid types, scope derived from file paths, header at most 72 characters excluding the emoji, subject/body/breaking-changes rules. Load when writing, reviewing, or generating a commit message.
- ▌ Working Agreements · carlosferordunaAlways-on engineering contract for this project - language rules, security, architecture, package manager, timestamps, logging, and agent workflow, plus an index of the stack skills. Load at the start of any coding, review, or commit task; load the relevant stack skill on demand.