01-mofa-studio-core
Core architecture of MoFA Studio: plugin system, shell/app boundaries, state coordination, theme and dark mode, and timer/event lifecycles. Use when changing architecture, refactoring, or adding cross-cutting b...
Discover Business skills, compare source repositories and read the instructions for each workflow.
Core architecture of MoFA Studio: plugin system, shell/app boundaries, state coordination, theme and dark mode, and timer/event lifecycles. Use when changing architecture, refactoring, or adding cross-cutting b...
Onboard to the MoFA Studio repository, run the app and dataflows, and choose the right MoFA Studio skill. Use when setting up the workspace, building/running, or deciding which part of the system to edit (app,...
Audio pipeline details for MoFA Studio: device selection, mic monitoring, AudioPlayer buffer behavior, and participant tracking. Use when modifying audio code or diagnosing audio issues.
Provider settings and user preferences in MoFA Studio. Use when editing provider UI, saving preferences, or wiring API keys and defaults.
Troubleshooting and operational reference for MoFA Studio: common errors, Dora issues, Makepad pitfalls, and checklists. Use when debugging or validating fixes.
Run and deploy MoFA Studio via Nix or manual builds, including dataflow startup and environment variables. Use when launching the app or preparing a dev environment.
Create or modify MoFA Studio apps, screens, and shell integration. Use when adding a new app, changing an existing app, or wiring app lifecycle (timers, dark mode, dataflow).
Makepad UI patterns in MoFA Studio: live_design layout, event handling, apply_over usage, shader-driven theming, and animation lifecycles. Use when editing UI or behavior.
Dora dataflow authoring and wiring for MoFA Studio dynamic nodes. Use when editing voice-chat.yml, adding dynamic nodes, or debugging dataflow connections and signals.
Generates and edits images via Gemini API. Use when creating new images or modifying existing ones.
Automates server configuration and multi-server deployments. Use when writing Ansible playbooks, setting up SSH auth, or checking deployment diffs.
Creates ast-grep patterns for structural code search. Use when finding functions/classes by structure, refactoring code, or when grep returns too many false positives.
Adds docstrings, comments, and WHY/DECISION tags to code. Use when documenting functions/classes with language-specific standards (JSDoc, PEP 257, GoDoc).
Provides Spring Boot API development standards. Use when implementing response formats, logging, i18n, or exception handling patterns.
Configures Claude Code hooks for projects and skills. Use when setting up lint, test, or format hooks in .claude/ directory, or applying hook recipes to skills via SKILL.md frontmatter.
Creates and manages Claude Code rules files. Use when creating .claude/rules/ files or applying conditional rules to specific files/situations.
Creates and manages Claude Code skills. Use when creating new skills, updating existing skills, or converting repeated prompts into reusable skill packages.
Applies TDD workflow to development. Use when implementing features, fixing bugs, or refactoring with test-first approach. Detects AI anti-patterns.
Provides DDD layered architecture patterns. Use when designing domain-centric systems or structuring complex business logic.
Measures code structure metrics (coupling, cohesion, complexity, call graph). Use when analyzing code quality quantitatively, checking architectural health, or reviewing structural changes.
Creates PowerPoint presentations via python-pptx. Use when building slides for presentations, proposals, or planning documents.
Guides test writing and review. Use when writing new tests, reviewing existing tests, or diagnosing mock overuse (see Workflow 2).
Reviews code for security vulnerabilities. Use when implementing auth, handling user input, adding APIs, or before deployment. Checks OWASP Top 10, credentials, injection.
Generates draw.io diagrams for visualization. Use when creating architecture, sequence, flowchart, or AWS infrastructure diagrams.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.