Loading...
Loading...
Found 10 Skills
A comprehensive development team tailored for beginners, consisting of product managers, architects, designers, developers, and testers, guiding you through the entire process from concept to launch.
The sole global workflow control plane for the Phaser 4 game repository. Handles low-risk local work based on task authorization and deterministic risk classification, distinguishes user clarification decisions, and retains precise explicit approvals only for specific A4-A6 operations and their impacts.
C# Openness implementation of project, portal, and library lifecycle.
Entry point to the Context Mate toolkit - skills, agents, and slash commands that work with Claude Code's natural flow. Project lifecycle (/explore-idea → /plan-project → /wrap-session), session handoff across context windows, developer agents for specialized tasks, and quality auditing. Use when: starting new projects, understanding the toolkit, needing workflow guidance. "It's all about the context, maaate!"
Use this skill when the user wants to detach, archive, purge, or otherwise change the lifecycle state of an Obsidian project knowledge base.
Use when starting a new project, adding a major feature to an existing system, or when unsure which skills to run and in what order. Supports macOS, iOS, web, full-stack, voice agent, and edge/IoT+ML projects.
Manage Linear projects. Use when listing, creating, updating, or viewing projects.
Coordinates skills, frameworks, and workflows throughout the project lifecycle using pattern-based sequencing, goal decomposition, phase-gate validation, and multi-agent orchestration. Use when starting multi-phase projects, sequencing frameworks, decomposing goals into capability plans, validating phase-gate readiness, coordinating subagents, or designing MCP-based tool orchestration.
Coordinate a project from discovery through architecture, planning, implementation, verification, delivery and monitoring using an OWL knowledge mediator. Use for OntoLink, ontology-mediated project flow, sequential skills, compact context, knowledge relationships, recommendations, communication, warnings, progress, blockers, confidence and likelihood assessments.
Structured specification with explicit scope boundaries: user stories, acceptance criteria, out-of-scope definition, risks, and estimation. Positions before feature-design in the feature lifecycle pipeline. Use when: "write spec", "user stories", "define requirements", "scope this", "what should this do", "acceptance criteria", "define scope"