All categories
Development
Programming, frameworks, implementation, frontend, backend, and app development
- 65,763
- 2,741
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse development skills
Showing 11,881–11,904 of 65,763 skills
- Review ChangesReview the working-tree changes (vs main) for correctness, concurrency, architecture, testing, and API/doc issues — following .github/CODE_REVIEW.md — and return a severity-graded report. Scales the machinery to the diff size: a single code-reviewer agent for a small change, or a fan-out-and-verify Workflow for a large/multi-unit one. Produces findings; it does not apply fixes (the caller does).Votes: 0GitHub stars: 178
- LintLint code with swiftlint and swiftformatVotes: 0GitHub stars: 178
- Integration TestRun the TMDb integration tests against the live TMDb API (the Integration test plan; requires TMDB_API_KEY/USERNAME/PASSWORD). Use before a PR, or after model/fixture changes, to validate against real API responses — delegates to the tooling-runner agent (Haiku) and returns counts + failures, distinguishing genuine failures from transient live-API/env issues. For mocked unit tests, use /test.Votes: 0GitHub stars: 178
- FormatFormat code with swiftlint and swiftformatVotes: 0GitHub stars: 178
- Fix Pr ChecksFix the currently-failing status checks on the current branch's PR in one sweep — route each failing check to the right diagnosis skill (via a Haiku subagent, escalating to Opus on a repeat failure), apply and verify the fix, commit, and push once — then return a summary. Use standalone when CI is red, or as the check-fixing step invoked by /watch-pr. Repo is adamayoung/TMDb.Votes: 0GitHub stars: 178
- Fix Integration FailuresDiagnose and fix a failing scheduled (or standalone) TMDb Integration workflow run — re-run transients, or fix real drift on a branch off main, then PR and (optionally) merge. Use for the weekly Sunday Integration cron failure, or any red Integration run not tied to an open PR.Votes: 0GitHub stars: 178
- Document SwiftWrite and maintain high-quality Swift DocC documentation for the TMDb package, following its established `///` conventions. Use when adding or changing any public declaration (protocol, class, struct, enum, actor, model, property, initializer, method, typealias) and when keeping the DocC catalog in sync. This is the single source of truth for the project's documentation style — applied inline as you write, and followed by the `documentation-writer` agent for bulk sweeps.Votes: 0GitHub stars: 178
- Diagnose Integration FailureDiagnose a failing TMDb integration-test run — summarise the failure, rank the likely cause, and suggest a concrete fixVotes: 0GitHub stars: 178
- Diagnose Ci FailureDiagnose a failing CI workflow run (lint, markdown lint, build, or unit tests) — identify which job failed, the cause, and a concrete fixVotes: 0GitHub stars: 178
- DeliverTake a plan all the way to a ready-to-merge pull request — review the plan (scaled to risk), implement it test-first, code-review and fix, run the CI gate, open the PR, and watch it green. Use after you have an approved plan (from plan mode, or the Plan agent); pass `issue <n>` to deliver a specific GitHub issue you name, or `next` to take the top startable issue off the project board's Ready column — either way it re-verifies, claims and plans the issue first. Invoking it with a plan already...Votes: 0GitHub stars: 178
- Cut ReleaseCut a new TMDb release — work out the next SemVer version from the evidence, do the pre-tag housekeeping a tag would otherwise freeze in place, draft release notes, then tag and publish the GitHub release. Presents the version (with its reasoning) and the full notes for approval and STOPS; nothing is tagged or published until you say go.Votes: 0GitHub stars: 178
- Capture KnowledgeCapture durable, project-specific learnings from the work just done into the knowledge/ base — gotchas, implementation quirks, things looked up or web-searched, live-API behaviours, and design decisions (as ADRs). Use before opening a PR (it runs automatically in /deliver), or any time you've learned something worth remembering. Records only non-obvious, reusable facts; skips anything already in the repo, CLAUDE.md, or git history.Votes: 0GitHub stars: 178
- Canon TddImplement features and fix bugs test-first, the Canon TDD way (test list → one test → make it pass → refactor → repeat). Use when implementing any new feature, endpoint, model, or method, fixing a bug, or executing a plan — write the test list and a failing test BEFORE production code.Votes: 0GitHub stars: 178
- BuildCompile the TMDb Swift package for the current platform to check it builds. Use to verify code compiles after changes — delegates the build to the tooling-runner agent (Haiku) and returns a concise pass/fail + errors-as-file:line summary, keeping logs out of context. To also compile the test targets, use /build-for-testing.Votes: 0GitHub stars: 178
- Build For TestingCompile the TMDb package AND all test targets (without running the tests) to catch test-code compile errors. Use after changing tests or shared code to check everything still builds — delegates to the tooling-runner agent (Haiku) and returns a concise pass/fail + errors-as-file:line summary. Differs from /build, which compiles only the library; to run the tests, use /test.Votes: 0GitHub stars: 178
- Trellis StartInitializes an AI development session by loading exact current-task facts, the workflow Phase Index, and the current workflow-owned continuation contract when a task is bound. Use when beginning a new coding session or re-establishing project context.Votes: 0GitHub stars: 8
- Trellis Finish WorkWrap up the current session: verify quality gate passed, remind user to commit, archive selected completed tasks, and report their status. Use when done coding and ready to end the session.Votes: 0GitHub stars: 8
- Team OsBootstrap e orquestração de sessão para Claude Code Agent Teams. Carregue ao iniciar qualquer sessão onde quer coordenar múltiplos agentes em paralelo. Verifica e configura o ambiente (AGENT_TEAMS, teammateMode), lê ou cria a smart-memory, pergunta o objetivo, analisa o paralelismo real e propõe um time dimensionado para máxima velocidade. Trigger: /team-osVotes: 0GitHub stars: 3
- Nextjs React Best PracticesMelhores práticas de performance para React e Next.js (App Router) — eliminar waterfalls, reduzir bundle, otimizar Server Components, data fetching, re-renders e Core Web Vitals. Use ao escrever ou revisar componentes React, páginas Next.js, data fetching (server ou client), ou ao investigar bundle size, hydration e lentidão de render.Votes: 0GitHub stars: 3
- Chappie FrontendCHAPPiE's React frontend. Use when modifying UI pages, components, Tailwind styling, or the chat streaming experience.Votes: 0GitHub stars: 4
- Chappie BackendBackend development for CHAPPiE. Use when working on FastAPI APIs, the modular runtime, vLLM, Groq, Ollama, training, or compatibility factories.Votes: 0GitHub stars: 4
- TerracesHow a step between terrace levels works in the overworld, what a cliff tile is, and how both boards draw it. Applies whenever changing terrace levels, walkability, placement of anything on the ground, or how the board draws a step.Votes: 0GitHub stars: 5
- Signature AbilitiesA signature ability is one invented ability per evolution family, numbered in the 200000 band and granted rather than rolled at birth. A legendary **group**, a region's **starter trio** and a pair of **counterpart families** each share one theme across their members. Applies whenever designing, naming, implementing or reviewing a signature ability.Votes: 0GitHub stars: 5
- Registry DescriptionsHow to write the one-line `description` a registered item, ability or move carries. Applies whenever adding an entry to a data registry under src/data, or rewording an existing line. The line describes this engine's behaviour, not the mainline's, and is derived from the data wherever the data already knows the answer.Votes: 0GitHub stars: 5