Explore skills
Showing 8131–8160 of 77104 skills
Create a hypothesis-driven, time-boxed spike ticket (Hypothesis/Budget/Kill Criteria/Disposition). Exempt from AgDR + coverage gates.
me2resh/apexyard
Stars: 549Claude CodeCodexClose a spike via the disposition gate — `--promote` files a [Feature] follow-up, `--discard` writes a memo.
me2resh/apexyard
Stars: 549Claude CodeCodexMigrate single-fork to split-portfolio mode (public framework + private portfolio) via gated destructive recovery flow.
me2resh/apexyard
Stars: 549Claude CodeCodexGenerate a weekly / monthly / launch stakeholder update — synthesises PRs, closed issues, AgDRs, and roadmap into a narrative.
me2resh/apexyard
Stars: 549Claude CodeCodexDeclare an active ticket so the ticket-first hook lets code edits through. Accepts `<N>` or `<owner>/<repo>#<N>`.
me2resh/apexyard
Stars: 549Claude CodeCodexProject snapshot — git state, open PRs + CI, recent merges, in-progress issue. Use `--briefing` for compact form.
me2resh/apexyard
Stars: 549Claude CodeCodexCreate a structured technical task ticket (driver, scope, ACs) for tech debt, infra, refactoring, or non-user-facing changes.
me2resh/apexyard
Stars: 549Claude CodeCodexFlat actionable task list across the portfolio with direct URLs — PRs to review, issues to triage, comments, failing CI.
me2resh/apexyard
Stars: 549Claude CodeCodexInteractive author for the architecture vision template — target, gap, migration, anti-scope, cadence.
me2resh/apexyard
Stars: 549Claude CodeCodexSTRIDE threat modelling — spoofing, tampering, repudiation, disclosure, DoS, EoP. Deep-dive for /launch-check security.
me2resh/apexyard
Stars: 549Claude CodeCodexFile 5–20 structured tickets in one flow — shared-context Qs once, 3-Q micro-interview per ticket, then per-ticket `tracker_create` (gh/glab/custom).
me2resh/apexyard
Stars: 549Claude CodeCodexStandalone re-entry to the capability tour + full glossary — replays the roles/skills/gates walkthrough and all five terms any time, respecting depth mode. No /setup or /handover coupling.
me2resh/apexyard
Stars: 549Claude CodeCodexSync the ApexYard fork with upstream — preview, merge-or-rebase on a sync branch, walk per-version migrations.
me2resh/apexyard
Stars: 549Claude CodeCodexLightweight 5-question pre-spec gate between /idea and /write-spec — catches "this isn't worth speccing" in 10 minutes.
me2resh/apexyard
Stars: 549Claude CodeCodexScaffold a [Feature]-class ticket for the thinnest end-to-end slice — one trivial path wired through every architectural layer. KEPT and grown; full SDLC (NOT exempt like /spike).
me2resh/apexyard
Stars: 549Claude CodeCodexWrite a feature spec or PRD from a problem statement or feature idea. Use when creating product requirements documents.
me2resh/apexyard
Stars: 549Claude CodeCodexWCAG 2.1 AA audit — perceivable, operable, understandable, robust criteria. Deep-dive for /launch-check accessibility.
me2resh/apexyard
Stars: 549Claude CodeCodexAnalytics audit — SDK config, event naming, funnel completeness, dashboards. Deep-dive for /launch-check analytics.
me2resh/apexyard
Stars: 549Claude CodeCodexGDPR + ePrivacy audit — consent, privacy policy, data handling, right-to-deletion, DPAs. Deep-dive for /launch-check compliance.
me2resh/apexyard
Stars: 549Claude CodeCodexDiataxis docs audit — tutorials, how-to, reference, explanation; checks README, API docs, deployment guides, changelog, staleness.
me2resh/apexyard
Stars: 549Claude CodeCodexGEO + AEO audit — `llms.txt`, `AGENTS.md`, AI-crawler robots, JSON-LD citation grounding. Sibling to /seo-audit.
me2resh/apexyard
Stars: 549Claude CodeCodexProduction readiness audit — 10-dimension go/no-go sweep (security, a11y, compliance, analytics, SEO, GEO, perf, monitoring, docs, behaviour-quality).
me2resh/apexyard
Stars: 549Claude CodeCodexObservability audit — logging, error tracking, health endpoints, alerting, runbooks. Deep-dive for /launch-check monitoring.
me2resh/apexyard
Stars: 549Claude CodeCodexPerformance audit — bundle size, image opt, lazy load, code split, caching, CWV. Deep-dive for /launch-check performance.
me2resh/apexyard
Stars: 549Claude CodeCodexTechnical SEO audit — meta, OG, sitemap, robots.txt, structured data, mobile, CWV readiness. Deep-dive for /launch-check SEO.
me2resh/apexyard
Stars: 549Claude CodeCodexClassify a skills CLI pull request from its description and patch, while respecting existing labels.
vercel-labs/skills
Stars: 39kClaude CodeCodexClassify a skills CLI pull request from its description and patch, while respecting existing labels.
vercel-labs/skills
Stars: 39kClaude CodeCodexHow to work in a Codebase Wiki project (the `codebase-wiki` starter pack): an agent-authored, source-grounded wiki of the surrounding codebase. Read when the project has a `wiki/` knowledge base with `architecture/`, `modules/`, `flows/`, `concepts/`, and `guides/` sections plus `wiki/OVERVIEW.md`, or when asked to generate or refresh a wiki of this codebase. Carries the per-folder rules and freshness + log discipline, summarizes the audience/depth knobs and source-reference convention, and bundles the full generate/refresh procedure in `references/`. Complements the platform `open-knowledge` skill; does not replace it.
inkeep/open-knowledge
Stars: 4.8kClaude CodeCodexHow to work in a Knowledge Base project (the `knowledge-base` starter pack). Read when the project has the three-layer source-grounded layout — `external-sources/` → `research/` → `articles/` — or when asked how this project is organized. Carries the layer model, per-folder rules, status flows, and log discipline so this guidance does NOT live inside template bodies or log.md. The three procedures live elsewhere: ingest in the platform `open-knowledge` skill, research and consolidate as their own sibling skills in this pack. Complements the platform `open-knowledge` skill; does not replace it.
inkeep/open-knowledge
Stars: 4.8kClaude CodeCodexFrame a new design proposal (RFC-shape) under proposals/ — problem before solution, named beneficiary and observable change, real alternatives, honest drawbacks, and a live open-questions backlog. Read when asked to frame a proposal, write an RFC, propose a design, pitch a change, draft a PRD-style design doc, or open a design proposal for review. Do NOT read to record a decision after it is accepted (use record-a-decision), to write an implementation spec (use write-a-spec), to write a postmortem (use write-a-postmortem), or to review or critique an existing design (use review-a-design).
inkeep/open-knowledge
Stars: 4.8kClaude CodeCodex