AI-First Development Methodology v2.0 for Claude Code — spec-driven pipeline with blocking gates, unified triad-based knowledge system, design pipeline, and automated validators. Session-aware, self-improving via quick-learning loop.
A shared system for capturing and reusing knowledge from work sessions, including a fixed format, similarity checks, counters, and adaptation tracking. It runs only when its signals indicate that learning is useful.
Autonomous one-shot cleanup and calibration of all skills in $AGENTSHOME. Removes 16 obsolete design skills (keeps photo-crop, content-card), purges codex references from active skills and triads, calibrates remaining skills against Anthropic best practices and the 250-line SKILL.md soft limit. Runs end-to-end without…
A checklist to run before deleting a project from a local computer. It checks Git synchronization, documentation, server state, and running local processes.
A code security review based on the OWASP Top 10, a list of common web-application security risks. It examines areas such as login checks, user input, database queries, and external APIs.
A lightweight prototyping mode for quickly trying an idea. It asks three to five questions, writes code directly without validation checks, and then decides whether to continue or archive the prototype.
Embeds accumulated triads from quick-learning into target skills as permanent instructions. Reads triads with Adapted=— from triad-index.md, analyzes each skill's existing logic, auto-applies new rules when no coverage exists, proposes refinements when partial coverage found. After embedding, updates Adapted field and…
Explicit-call only. Invoked by project-planning and tech-spec-planning as a gate before stack decisions, or manually via /stack-research. Not auto-triggered by keywords. Researches stack elements (libraries, APIs, services) against official documentation via parallel subagents, produces comparison tables, and…
A planning tool that breaks an approved technical specification into small task files. A technical specification is a written plan describing how a software change should be built.
A tool that writes a technical specification covering the software architecture, key decisions, testing approach, and implementation plan. It requires an existing user-spec.md file, which describes what the user needs.
A guide to planning and reviewing software tests. It covers choosing tests, checking their quality, and using the test pyramid, a strategy that balances different kinds of tests.
A method for finding the smallest set of TRIZ techniques that resolves an entire design contradiction. TRIZ is a problem-solving framework for improving systems when one change creates a competing drawback.
A skill for resolving conflicting development requirements, where one part of a system is expected to satisfy opposing conditions. It looks for existing resources in the code and data structure, then tests possible ways to separate the conflict by structure, timing, conditions, or relationships.
Write code with quality process - TDD, reviews (uses code-writing skill).
★not rated 2 17d agoA16 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: