Menú
Professional standards for Git version control, branching, and commit messages.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Protocol for QA, error verification, and skill evolution to prevent recurring bugs.
Guidelines for Domain-Driven Design and Clean Architecture dependency rules. Trigger: When creating new UseCases, Repositories, or planning module structure.
Guidelines for using Drizzle ORM with SQLite. Trigger: When writing SQL queries, migrations, or modifying schema definitions.
Expo Managed Workflow guidelines. Trigger: When configuring app.json, installing native libraries, or dealing with permissions/plugins.
FontStock Database Schema and Seeding. Trigger: When defining tables, relations, or initial data.
FontStock business logic for inventory (expiry, search indexing). Trigger: When calculating dates, validating product inputs, or implementing search filters.
| name | git-workflow |
| description | Professional standards for Git version control, branching, and commit messages. |
Follow these guidelines to maintain a clean, professional history.
Format: type(scope): subject
feat: A new featurefix: A bug fixdocs: Documentation only changesstyle: Changes that do not affect the meaning of the code (white-space, formatting, etc)refactor: A code change that neither fixes a bug nor adds a featureperf: A code change that improves performancetest: Adding missing tests or correcting existing testschore: Changes to the build process or auxiliary tools and libraries such as documentation generationgit commit -m "feat(auth): implement login screen validation"
git commit -m "fix(db): resolve foreign key constraint error in products table"
main: Production-ready code.develop (Optional): Integration branch.feature/short-descriptionfix/short-description or bugfix/short-descriptiongit pull origin maingit checkout -b feature/new-product-cardgit push origin feature/new-product-card## Summary
[Brief description of changes]
## Type of Change
- [ ] New feature
- [ ] Bug fix
- [ ] Refactor
## How was this tested?
- [ ] Manual verification
- [ ] Unit tests passed
## Screenshots (if UI change)
[Insert Screenshots]
npm run lint or npx expo typecheck before committing.