القائمة
Use when updating HealthBytes docs, README files, roadmap, setup/env docs, architecture docs, AI inspections, agent prompts, weekly reports, or documentation structure.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Automatically generates and updates the CONTRIBUTORS.md file by analyzing git merge history, identifying authors who have merged at least 2 branches, and formatting the output beautifully.
Use when asking for a team report, assigning tasks, updating task status, or managing the sprint board for HealthBytes. Triggers on "reporte del equipo", "asignar tarea", "dame un resumen del sprint", "qué están haciendo los chicos", "nueva tarea para", or any team/task management request.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when the user needs to change, update, or bump the app version of HealthBytes — mentions "versión", "version bump", "subir versión", "cambiar versión", "release", "nueva versión", or asks what version the app is on.
Mobile-first design and engineering doctrine for iOS and Android apps. Covers touch interaction, performance, platform conventions, offline behavior, and mobile-specific decision-making. Teaches principles and constraints, not fixed layouts. Use for React Native, Flutter, or native mobile apps.
Use when repeated project mistakes, review feedback, failed commands, onboarding friction, or team workflow lessons should become reusable AI development behavior for this repo.
| name | HealthBytes-docs |
| description | Use when updating HealthBytes docs, README files, roadmap, setup/env docs, architecture docs, AI inspections, agent prompts, weekly reports, or documentation structure. |
Keep HealthBytes docs current without creating duplicate sources of truth or root-folder clutter.
Before editing docs:
.cursorrules..agents/router.json..agents/agents/tasks.json for an explicit docs task.docs/README.md.docs/plans/2026-06-04-documentation-roadmap-reboot-design.md if the work touches the documentation reboot.Use the right owner:
| Question | Source |
|---|---|
| Product vision | docs/product/vision.md |
| Users and market | docs/product/market-and-users.md |
| Health criteria | docs/product/health-rules/ |
| MVP | docs/roadmap/mvp.md |
| Roadmap status | docs/roadmap/weekly-status.md |
| Backend architecture | docs/development/architecture/backend.md |
| Frontend architecture | docs/development/architecture/frontend.md |
| Infrastructure | docs/development/architecture/infrastructure.md |
| Envs | docs/development/setup/envs.md |
| AI agents | docs/ai/agents/ |
| AI inspections | docs/ai/inspections/ |
| Executive reports | docs/executive/ |
| QA/security/release process | docs/operations/ |
Update the source of truth first. Update indexes and pointers second.
docs/ai/inspections/.docs/executive/.README.md concise.docs/README.md as navigation, not a long status document.HealthBytes gives recommendations, not medical guarantees.
Allowed:
Avoid:
When moving or rewriting docs:
keep, rewrite, merge, reference, or delete_later.Minimum checks:
git status --shortjq empty .agents/router.jsondocs/, .agents/router.json, and this skill.If docs QA scripts are restored from legacy, run them only after updating their expected paths.