Skip to main content
NeVibeCode · author · 14 items

gotalab: skills, plugins and MCP servers

Every card from gotalab repositories on GitHub: what each one does, an install command and example prompts. Inside: 11 rules and 3 skills. They work in Claude Code, Codex, Cursor — 9 platforms in total.

Repositories2

design-synthesis rule design-synthesis is a rule for analyzing gathered requirements before writing a design document. It uses generalization, build-or-adopt, and simplification to set the solution's scope. CX Codex +1 ★ 3,774repo stars steering-principles rule steering-principles defines standards for project memory files, capturing architecture patterns without cluttering context with exhaustive file catalogs. CX Codex +1 ★ 3,774repo stars skill-evaluator skill skill-evaluator audits agent skills against Anthropic's authoring guidance, checks SKILL.md conventions, and produces scored findings with practical fixes for a pre-release review. CX Codex +1 ★ 423repo stars git-branch-cleanup skill git-branch-cleanup sorts local branches by merge status and remote tracking, then deletes the ones you pick after a confirmation. Useful once git branch gets out of hand. CX Codex +1 ★ 423repo stars tasks-parallel-analysis rule The tasks-parallel-analysis rule sets checks for marking tasks in tasks.md as parallel work. Use it when an agent drafts an implementation plan and needs to account for dependencies. CX Codex +1 ★ 3,774repo stars requirements-review-gate rule The requirements-review-gate rule halts work and requires fixing the requirements draft before requirements.md is written. It validates scope coverage, EARS format compliance, and structural quality. CX Codex +1 ★ 3,774repo stars design-review-gate rule design-review-gate audits draft architectures before generating design.md. It links requirement IDs to concrete components and prevents speculative interfaces. CX Codex +1 ★ 3,774repo stars ears-format rule The ears-format rule formats acceptance criteria with EARS patterns. Use it when a specification needs clear conditions, subjects, and system responses. CX Codex +1 ★ 3,774repo stars design-discovery-full rule The design-discovery-full rule systematically maps requirements, existing code, technologies, and risks before design begins. It ensures architectural choices rest on facts rather than assumptions. CX Codex +1 ★ 3,774repo stars design-review rule design-review reviews technical design documents before coding starts and issues a GO/NO-GO verdict. Caps feedback at three critical issues tied directly to project requirements. CX Codex +1 ★ 3,774repo stars cc-sdd-new-agent skill The cc-sdd-new-agent skill guides a new coding-agent integration in cc-sdd, from official-format research and planning to implementation checks. CX Codex +1 ★ 3,774repo stars gap-analysis rule The gap-analysis rule structures the analysis of your existing codebase, identifies what's missing for a feature, and helps you decide whether to extend existing components or build new ones. CX Codex +1 ★ 3,774repo stars tasks-generation rule tasks-generation guides AI coding agents to generate structured, dependency-ordered technical task plans from specifications without leaking low-level code details. CX Codex +1 ★ 3,774repo stars design-principles rule The design-principles rule sets checks for architecture, types, documentation, and Mermaid diagrams. Use it when drafting design.md or reviewing component boundaries. CX Codex +1 ★ 3,774repo stars

More in NeVibeCode

Project sponsors

Companies that keep this analytics open