Loading...
Loading...
Found 5 Skills
Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.
Comprehensive end-to-end validation of the Archon Web UI using browser automation and codebase review. Use when: User wants to validate, test, or audit the Archon web interface, find UI/UX bugs, test workflow management, verify parallel agent orchestration, or run comprehensive browser-based E2E tests. Triggers: "validate ui", "test the ui", "e2e test", "browser test", "validate archon", "test archon ui", "ui audit", "ux review", "comprehensive test", "validate everything". Capability: Starts Archon, runs exhaustive browser automation tests via agent-browser CLI, performs codebase review, and produces a detailed bug/UX report. NOT for: Unit tests (use `bun test`), CLI-only validation (use /validation:validate-simple).
Perform 12-Factor Agents compliance analysis on any codebase. Use when evaluating agent architecture, reviewing LLM-powered systems, or auditing agentic applications against the 12-Factor methodology.
Read-only whole-project deep audit — architecture and module boundaries, documentation-vs-code fidelity, design-principle adherence (YAGNI/KISS/SOLID), and extensibility (how easily someone builds from source and adds a new provider/plugin/adapter) — producing a prioritized report with a SHIP / FIX / BLOCK verdict. Framework- and language-agnostic. Use when the user asks to 'audit/analyze the architecture', 'review the whole codebase design', 'does the code match the README/docs', 'how hard is it to add a new X', 'is this codebase ready to build on', or 'проведи глубокий анализ проекта', 'оцени архитектуру', 'соответствует ли код документации'. Do not use for a single diff/PR (use awesome-code-review), a named vulnerability (awesome-security-audit), runtime latency/memory (awesome-performance-audit), public-client disclosure (awesome-leak-audit), comment/naming cleanup (awesome-code-cleanup), or design-stage shaping of a new system or API (awesome-design-doc, awesome-api-design).
Analyze a task specification, review the codebase, and output a detailed assessment and success criteria. Use when user provides a new ticket or description to understand scope, risks, and definition of done before implementation.