community
claudeCurated open-source community skills — vendored for zero-friction access across all projects.
7 skills
Full-stack web application delivery platform. Orchestrates requirements, architecture review, frontend (FDS), backend (Koa + PostgreSQL), build verification, testing, code review, and deployment across a team of specialist agents.
Plugin wai from marketplace ccube-agent-plugin-marketplace in LifeSG/ccube-agent-plugin-marketplace. Commands read from the repo's manifest — 13 days ago.
cc-code-reviewPrincipal engineer code review workflow — orchestrates 5 specialized review subagents plus always-on security verification and a second synthesis pass for comprehensive analysis covering security, architecture, production readiness, code standards, and strategic impact. Supports 3 scope strategies:
cc-contribute-waiGuide for creating, reading, updating, or deleting skills, agents, or instruction files. Use when a user wants to add a new skill, build a new agent, contribute to the WAI plugin, or make any CRUD change to Copilot customization files — regardless of how the request is phrased (e.g., "create an agen
cc-create-epEnhancement Proposal (EP) creation — stepwise, KEP-style EP authoring with template discovery, parallel codebase research, and structured Part-1 / Part-2 / Part-3 generation. Use when creating or drafting an EP or feature design document. Describe the feature or change to capture in an EP. Include a
cc-create-mai-agentCreate a project-local (MAI) agent for BYOA — generates a properly-structured agent file at wai/byoa/ that Maestro discovers by filename and routes to instead of WAI defaults. Use when: user wants to add their own frontend or backend specialist, says "create a MAI agent", "add my own agent", "bring
cc-create-prdProduct Requirements Document (PRD) creation for product managers — guided feature-brief authoring, JIRA-format epic/story generation, and sprint-ready work breakdown. Use when writing feature requirements, creating JIRA tickets, or decomposing a feature into deliverable chunks. Integrates as option
cc-design-systemFlagship Design System (FDS) knowledge for @lifesg/react-design-system — component catalogue, token reference, and Figma-to-FDS mapping heuristics. Use when implementing UI with FDS components or analysing which Figma elements can be fulfilled by FDS.
cc-fullstack-viteCreate a new full-stack application with Vite + React + Flagship Design System frontend and Koa + PostgreSQL backend, all in a single project folder. Use when the user wants a full-stack app with a database, or asks for a project with both frontend and backend.
cc-git-commitAtomic commit workflow — groups changed files into logical commits and produces Conventional Commit messages prefixed with branch name and author initials. Use when performing any git staging, committing, or when the user asks to save, commit, or push work. Optionally describe what changed, e.g. "co
cc-plan-implementationImplementation plan generation — decomposes an EP or task description into a parallelised, phase-based workplan with a Mermaid dependency graph, critical path analysis, per-task agent prompts, and a parallel dispatch table. Use when creating an implementation plan for an EP or any task description.
cc-rabbit-deployGCC deployment via Rabbit Deploy — initialize a local project with git, configure the Rabbit Deploy GitLab remote with a Project Access Token, and push to trigger automatic deployment. Use when a user wants to deploy their project to GCC using Rabbit Deploy, set up version control for the first time
cc-swe-coachGuide non-developers through software engineering workflows. Use when someone who works alongside developers (PM, designer, team lead, QA manager, technical writer) asks how to perform an engineering activity — making a feature change, fixing a bug, or requesting a code review.
cc-vite-react-dsInitialize a new Vite + React + TypeScript frontend project with Flagship Design System (@lifesg/react-design-system) pre-configured. Use when user wants to scaffold a new web application using FDS components.
cc-write-e2e-testPlaywright setup and test authoring for any web application. Use when setting up Playwright from scratch, fixing a misconfigured Playwright project, or writing new spec files. Triggers on: "set up Playwright", "initialise E2E", "Playwright not working", "write a test", "add test coverage", "create a
Code Review Architectural SubagentSystem design, scalability, API contract evolution, test coverage, and architectural pattern analysis for code reviews
Code Review Production Readiness SubagentDeployment risk, operational readiness, monitoring, and performance analysis for code reviews
Code Review Security Verification SubagentVerifies exploitability of CRITICAL/HIGH security findings through code flow analysis
Code Review Security SubagentSpecialized OWASP Top 10 security vulnerability detection for code reviews
Code Review Standards SubagentProject-specific coding standard and instruction file verification for code reviews
Code Review Strategic SubagentTechnical debt, extensibility, long-term maintainability, and evolution path analysis for code reviews
MaestroDefault routing agent for the WAI plugin. Classifies every user prompt and dispatches to the correct specialist. Invoke for ALL prompts in a WAI-enabled workspace — this agent replaces direct harness routing with reliable intent classification and project context detection. Handles: frontend builds
WAI Backend EngineerHands-on backend implementation specialist for Vite + Koa + PostgreSQL projects. Invoke when: (1) the user asks to build, create, or implement API endpoints, routes, or server-side features, (2) database migrations or seed data must be created, (3) backend build or test errors need fixing, or (4) se
WAI FDS EngineerHands-on React implementation specialist using Flagship Design System (FDS / @lifesg/react-design-system). Invoke when: (1) the user asks to build, create, or implement a page, feature, or UI component in a project that uses @lifesg/react-design-system, (2) a design spec or implementation brief need
WAI Product ManagerProduct thinking specialist for defining problems, scoping MVPs, and writing user stories. Invoke when: (1) vague problem description or "what should I build" question, (2) scope, MVP, or requirements discussion needed, (3) user stories need to be written, or (4) the user describes a problem rather
govtech-mcpconnects to: https://mcp-gw.seed.tech.gov.sg/mcp
Curated open-source community skills — vendored for zero-friction access across all projects.
7 skills
Release, deploy, and smoke-test knowledge for the Celerity pillar (SupportGoWhere): an end-to-end deploy/release runbook and a read-only site health check. Sanitised for public use; project IDs are configured per deployment.
2 skills
Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).
39 skills
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
15 skills · hooks
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
6 skills
Talk like caveman. Cut filler. Keep technical details explicit.
22 skills · 1 command · 3 agents · hooks
Persistent memory for Claude Code: the next session starts where the last one left off.
29 skills · 1 MCP server · hooks
tasteskill 2.5.1: professional company websites at the figma.com and x.ai level, with one section per screen, real photographs, real product UI, effects kept for tech and gaming pages, and a real-browser checker and finish gate.
1 skill
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.