Standalone Phase 1 of SAP UI testing. Discovers the configured test folder and target system, downloads one complete ABAP source snapshot, then READS that source and captures the full picture in three reference artifacts — flow.md (functional flow), units.md (per-unit input/output inventory), and findings.md (the…
A workflow for choosing mathematical models and shaping a modelling paper around its scoring criteria. It also defines coordination rules for keeping a long modelling task on track.
Write a short implementation plan or a longer execution plan before coding. Use when starting new work, when a ticket needs clearer boundaries, when a change spans multiple files or interfaces, or when a multi-hour task needs a living plan.
A game-design document writer that turns research, game ideas, player goals, testing plans, diagrams, and production limits into proposals, design documents, or funding pitches.
Import existing project documentation into a block-level PlanWeave Plan Package and validate it through the PlanWeave CLI. Use when importing PRDs, roadmaps, issue sets, architecture notes, or another strong source plan.
Initialize a new project. Creates the PRD and a prioritized feature map. Run once at the very start of a new project. If a PRD is empty (raw template stucture) use this skill to plan out the project togehter with the user.
Author and manage standalone Codex strategy skills named strategy- when the user wants an agent-readable investment strategy, library entry, entry or exit criteria, sizing rule, evidence standard, or decision-ready procedure. Start tool-using management with $tcx-strategy on the first meaningful line of a root turn…
A tool that turns a travel plan into a single HTML page designed for phones and offline reading. The page can include an interactive map, a daily timeline, and reminders to book things before departure.
Work with IFC / BIM files (.ifc, .ifcx, IFC2X3 / IFC4 / IFC4X3 / IFC5) from the terminal using the ifc-lite CLI — inspect, query, validate (IDS), export (CSV/JSON/IFC/glTF/Parquet), create elements, merge, convert schema versions, diff, clash-check, run BCF collaboration, and script the SDK. Use whenever a task…
Comprehensive guidance for building web apps with opinionated defaults for tech stack, design system, and code standards. Use when user wants to create a new web application, dashboard, or interactive interface. Provides tech choices, styling guidance, project structure, and design philosophy to get users up and…
FOLLOW THE STATE MACHINE IN SKILL.MD. When user says 'continue': (1) FIRST: Run pwd, (2) Announce STATE: CHECKSTATUS, (3) Read .claude/session.md to check Status field, (4) Route based on Status. NEVER auto-advance tasks. NEVER use TodoWrite. NEVER create git commits.
Autonomous multi-agent mission orchestrator. Decomposes a mission into tasks, spawns sub-agents for each step, reviews output against exit criteria, and chains tasks automatically with retry. State persists to disk so missions survive context loss. Triggered by the Conductor UI or by direct user request.
Software design philosophy guide based on John Ousterhout's "A Philosophy of Software Design." Use this skill during: code reviews, architecture discussions, API design, module decomposition decisions, refactoring guidance, complexity analysis, naming and commenting improvements, error handling strategy design.…
Use when designing the variables namespace for an EpicStaff flow, translating business requirements into node graph contracts, or deciding which node type fits a responsibility.
A guided method for analyzing real-life problems using ideas adapted from Mao Zedong’s Selected Works. It focuses on facts, the main problem, the current stage, available forces, and testing conclusions in practice.
A readiness check for moving a game project from one development stage to the next. It checks required documents, quality conditions, and blockers, then can record the new stage in a project status file.
A skill that generates structured PRD documents from business context. PRD means product requirements document: a written description of what a product or feature should do and why.
A structured software-development workflow based on the SDD-RIPER method, with stages for clarifying goals, mapping code, writing specifications, and tracking work.
★not rated 325▲
+1 12d agoA87 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: