All authors
Claude Skills by leosimini
github.com/leosimini15 skills0 installs12 views
- Build StoryBuild one backlog story end to end with independent checks — done-contract from its dimensions and invariants, acceptance tests written by the verifier before any code, implementation, a cold review and an adversarial breaker before landing (again after the rebase if main moved), verification in the running app, then merge. Use when the user says "build the next story", "implement AUTH-003", "next", "continue the backlog", "construí la siguiente historia", "implementá AUTH-003", "seguí con el...Votes: 0GitHub stars: 2
- Check BugbashFull bug bash of a Keelokit project across every dimension (data, API, contracts, logic, integrity, auth, UX, UI, web, mobile, i18n, copy, a11y, security, NFRs, config, ops, and dx, docs and packaging for what developers use) — parallel lenses on the running app with seeded personas, adversarial validation of each finding, fixes at the root cause, and, for every class of bug, a new automatic check so it can't come back. Use when the user says "bug bash", "cazá bugs", "revisá todo", "buscá err...Votes: 0GitHub stars: 2
- Check HealthCheck and repair the health of a Keelokit project's harness — rules without enforcers, enforcers that point nowhere, expired or incomplete exceptions, gaps in docs/context, malformed stories — and add new rules with their checks. Use when the user says "doctor", "chequeá el harness", "¿está todo en orden?", "salud del proyecto", "agregá una regla", "esto no puede volver a pasar", "registrá una excepción", or when the doctor (`python3 .keelokit/bin/doctor.py`, `pnpm run doctor`) or CI's doctor...Votes: 0GitHub stars: 2
- Check SecuritySecurity and privacy review of a Keelokit project, in depth — a map of every piece of personal data (what, why, where, who sees it, how long), the privacy law of each market, a threat model of the critical journeys, dependency and container scans, an OWASP ZAP scan of staging, and checks for PII in logs and error reports, data export and deletion, retention and encryption. Fixes at the root with a test, and leaves a check per class of problem, like the bug bash. Use when the user says "securi...Votes: 0GitHub stars: 2
- Harness UpgradeMaintenance of the harness, not of the app — bring a Keelokit project up to a newer Keelokit version: the house rules, the doctor and the guard, CI, git hooks and base configs, merged with Copier on a branch, without touching the product's code (apps, migrations, E2E, translations). Use when the user says "upgrade keelokit", "update the harness", "actualizá keelokit", "actualizá el harness", "traé la última versión del template", after `claude plugin update`, or when the dashboard or doctor s...Votes: 0GitHub stars: 2
- KeelokitEntry point of the Keelokit harness. Use when the user says "keelokit", "/keelokit", "dónde estamos", "qué sigue", "what's next", "estado del proyecto", "retomemos", or opens a session in a Keelokit project and asks what to do. Reads the project state and answers where the project is, what comes next and what decision is waiting for the human; routes to project-new, project-adopt, plan-intake, plan-backlog, build-story, check-health, project-dashboard or project-report.Votes: 0GitHub stars: 2
- Plan BacklogTurn a product's context and PRD into a backlog — epics, stories as vertical slices, consolidated, prioritised and grouped into waves that never touch the same files. Use when the user says "armá el backlog", "generá las historias", "stories", "épicas", "consolidá el backlog", "priorizá", "planificá las waves", "backlog", when project-new reaches gate 5, or after a new feature intake. Also re-plans an existing backlog without renumbering finished stories.Votes: 0GitHub stars: 2
- Plan IntakeInterview the user in their language (and read what already exists) to write a product's context in docs/context — problem, users, domain, constraints, environments, and every open gap with owner and question. Use when the user says "entrevistame", "intake", "relevamiento", "contexto del proyecto", "tengo una idea", "armá el contexto", "gather requirements", when project-new reaches gate 1, or when a new feature needs context the project doesn't have. Only asks what the house harness doesn't ...Votes: 0GitHub stars: 2
- Project AdoptBring an existing repository (brownfield) under the Keelokit harness without touching its code — installs only .keelokit/, maps each house rule to the checks the repo already has, registers what it can't meet yet as dated exceptions, builds docs/context from what exists, and seeds a backlog from a diagnosis of the real code. Use when the user says "adoptá este repo", "sumá keelokit a este proyecto", "proyecto existente", "brownfield", "aplicá el harness acá", "adopt", or when /keelokit runs i...Votes: 0GitHub stars: 2
- Project DashboardOpen or refresh the project's Keelokit dashboard — one short, branded page for day-to-day work, kept live — where the project is, the next step with its command to copy, what waits for you (approvals, decisions from bug bashes and security reviews, environments, harness updates), the development waves with every story linked to its file, health and environments, and links to the project's documents. Built from the repo, so it always reflects where the project really is. Use when the user says...Votes: 0GitHub stars: 2
- Project NewStart a new product from zero with the Keelokit harness — intake interview, PRD, stack decision, monorepo skeleton with CI and staging from day 1, and the first backlog. Use when the user says "nuevo producto", "arrancar un proyecto", "kickstart", "quiero construir una app", "armá el proyecto", "new product", or when /keelokit finds no project and the user wants one. Resumes from the pending gate when .keelokit/state.toml exists.Votes: 0GitHub stars: 2
- Project ReportGenerate the project's complete status report — a read-only Keelokit page with every stage and its documents (context, gaps, PRD scope and metrics, stack, backlog by wave and by epic), bug bashes and security reviews with their findings, environments, decisions and history — to share with someone or export as a file. Use when the user says "reporte", "reporte completo", "informe de estado", "exportá el estado", "para compartir", "status report", "export", "share the project's status", or pres...Votes: 0GitHub stars: 2
- Ship ReleaseRelease a version of the product — pick the next semver from what landed since the last tag, write the CHANGELOG entry in words users understand (stories done, bug fixes, what changed for them), tag vX.Y.Z on main after the user says yes, and follow the production deploy, which waits for a person to approve it in GitHub. Use when the user says "release", "sacá una versión", "publicá", "pasemos a producción", "versioná", "ship it", "deploy to production", after a wave or a bug bash, or when th...Votes: 0GitHub stars: 2
- Ship SetupSet up where the product runs — staging and production — for people who have never deployed anything. Writes docs/deploy.md, a step-by-step guide with a checklist per environment, does every step that doesn't need the user's credentials or money (Fly.io apps and config, GitHub environments with production approval, deploy tokens piped straight into GitHub secrets), walks the user through the rest (accounts, logins, payment, their own API keys), and verifies each step for real. Use when the us...Votes: 0GitHub stars: 2
- Run LocalRun the product's Expo app and its API on this Mac, on an Android phone, an Android emulator or an iOS Simulator, in one command — the script checks what the Mac is missing, shows it all at once, installs it after one yes, starts the database and the API, launches the app (without rebuilding what is already installed), and when a step fails keeps the error so Claude can read it, propose the fix and try again. It also reports what is running, shows its logs and cleans native build state, as da...Votes: 0GitHub stars: 2