Orchestrate the full lifecycle of delegated technical work: explore the problem space, author an implementation plan, then coordinate implementation across team members. This pipeline composes leaf skills (systematic-exploration, implementation-plan-authoring) into a leader workflow with explicit phase gates…
Orchestrate the full lifecycle of ecosystem capability improvement: research the current state of skills and scenarios in a target area, analyze capability gaps with structured decision trees, and plan cross-cutting implementation that spans skills, scenarios, CLIs, and ecosystem registries. This pipeline composes…
Orchestrate the full lifecycle of delegated problem resolution: triage severity and blast radius, drive hypothesis-based investigation through team members, then coordinate the fix with regression testing and verification. This pipeline composes leaf skills (triage-methodology, scientific-debugging) into a leader…
Daily strategic sync and idea generation session — the single interface through which you steer the entire Vrooli project. This skill guides a structured conversation that covers decision triage, strategic review, and open-ended brainstorming, ensuring nothing falls through the cracks while preserving space for…
Prioritize navigation integrity: every control that changes location, view, or mode should take the user where they reasonably expect to go, with honest labels and clear feedback.
Prioritize runtime performance and perceived responsiveness across this entire scenario. Do not break functionality or regress tests; all changes must maintain or improve completeness.
Methodology for finding and loading relevant prompt-manager skills before creating implementation plans. Ensures plans are informed by existing organizational knowledge and that executing agents can load the same context.
Analyze how scenarios consume packages/{{PACKAGE}}/, identify repeated friction and contract drift, and produce a prioritized improvement backlog that makes the package more reliable and easier to use without breaking downstream consumers.
Harden packages/{{PACKAGE}}/ for reliability and usability: stabilize contracts, improve default human output (when relevant), add tests and docs, and prove changes via a downstream compat set. Default posture is brownfield-safe and non-breaking.
Session constraints for work on shared platform code (for example packages/, shared templates, shared contracts). These boundaries keep changes brownfield-safe and compatible with downstream scenarios.
Prioritize overall quality, coherence, and finish across the scenario. Do not break functionality or regress tests; all changes must maintain or improve completeness. Avoid large structural refactors or new feature work — focus on refinement, not reinvention.
Prioritize performance-first 3D development using React Three Fiber patterns that prevent re-renders, optimize animation loops, and maintain architectural coherence across 3D scenes.
Prioritize code quality, structure, and maintainability across this scenario’s implementation. Do not change the intended behavior, regress tests, or weaken safety guarantees; all changes must maintain or improve completeness.
Create a durable research conclusion file that captures the research question, methodology, findings, and actionable next steps. This skill standardizes how research results are documented so any future agent can understand what was investigated, what was found, and what to do next.
Reference knowledge for creating and improving Vrooli scenarios. Use this skill when authoring implementation plans for idea-type backlog items so the plan includes the correct operational steps, CLI commands, and tool integrations.
Assess whether a scenario's uncommitted changes are ready to commit by querying the git-control-tower unified review endpoint for code health signals, then reviewing the actual git changes for coherence and intent.
Convert any Vrooli scenario into a cross-platform desktop application (Windows, macOS, Linux) using the scenario-to-desktop CLI. The tool creates Electron wrappers that connect to your running scenario.
Apply the scientific method to debugging: generate falsifiable hypotheses, design experiments (tests) to validate them, and systematically narrow down to the root cause. This methodology produces regression tests and documented findings that prevent recurrence.
★not rated 56 todayA0 tokens
AGPL-3.0
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: