with one click
skills
skills contains 17 collected skills from hoonzinope, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Audit code for bugs, security, and refactor candidates. Logs findings to .documents/review/ without modifying source code.
Operate Conductor context-driven development. Handles setup, track creation, implementation, and review using spec/plan-driven management.
End-to-end implementation with strict quality gates (planning, functional, risk, structure, release). Use for release-ready changes with explicit go/no-go decisions.
Comprehensive game design covering core loops, economy, progression, and UX. Audits growth and friction in .documents/game/.
Triage bugs, propose hypotheses, and implement fixes. Logs changes in .documents/_ops/ and .documents/review/.
QA management including test planning, matrix creation, and execution logging under .documents/qa/.
SwiftUI development and iOS UX/HIG compliance. Use for building features, refactoring views, and HIG audits (targets, Dynamic Type, semantic colors, modern APIs, iOS 26+ Liquid Glass).
Requirements translation into plans and specs. Audits plans for risks and gaps in .documents/plan/.
Integrated UI/UX skill combining data-driven design intelligence (styles, colors, typography, UX datasets) with structured documentation (user flows, IA, screen specs, audits). Use for end-to-end UI/UX design, implementation guidance, and documenting design decisions in .documents/uiux/.
Produce UI copy (buttons, errors, empty states, toasts) aligned to tone and product goals, writing to .documents/uiux/UIUX.md.
Record important design or tradeoff decisions with context and rationale in .documents/_ops/DECISIONS.md.
Audit dependencies for updates, licensing, vulnerabilities, and unused packages; write findings to .documents/_ops/DEPENDENCY_AUDIT.md without changing code.
Maintain and organize .documents by removing duplication, adding links, and marking the latest sources; update .documents/_ops/DOCS_INDEX.md.
Create a performance measurement plan detailing where, what, and how to measure; write to .documents/_ops/PERF_PROFILE_PLAN.md.
Recommend the next 1–3 skills to run (minimal effective workflow) based on .documents state and enabled skills, then log it.
Produce release notes and migration guidance from recent changes; write to .documents/_ops/RELEASE_NOTES.md.
Perform a security review focusing on auth, secrets, validation, and logging; write findings to .documents/_ops/SECURITY_AUDIT.md without changing code.