fusengine
UserRedefining development through cognitive automation and collaborative agent systems.
Categories
Indexed Skills (49)
apex-methodology
Use when starting ANY development task -- feature, bug fix, refactor, hotfix (triggers: implement, create, build, fix, add feature, refactor, develop).
elicitation
Use when an expert agent self-reviews and self-corrects code after the Execute phase, before sniper validation (BMAD-METHOD elicitation techniques).
exploration
Use when exploring an unfamiliar codebase -- architecture analysis, pattern detection, dependency mapping, rapid discovery.
think-in-code
Use when analyzing multiple files, auditing a codebase, scanning dependencies, or counting lines -- one Bash pipeline beats N sequential Read calls.
design-android
Use when designing an Android screen or flow — deliverable is a device-framed HTML mockup and developer handoff spec, never Compose code.
design-ios
Use when designing an iOS or macOS screen or flow — deliverable is a device/window-framed HTML mockup and handoff spec, never SwiftUI code.
design-method
Use when starting any design task — resolves register, sets the 3 dials, locks Gate 0, and routes to the right move and target skill.
design-motion
Use when adding or reviewing motion on an already-settled layout or component — never to hide or compensate for an unfinished one.
design-review
Use when a design deliverable is about to be reported done — the final quality gate after design-motion or a mobile mockup.
design-system
Use when starting any design task, before choosing or auditing a color/type/spacing token or writing design-system.md — routing step 1.
design-web
Use when building or revising a marketing/landing/campaign page, register `brand` locked at Gate 0 — use design-webapp for app screens instead.
design-webapp
Use when building or extending a dashboard, SaaS screen, or any authenticated app surface — use design-web instead for a marketing site.
ux-copy
Use when writing or reviewing any visible copy — headlines, buttons, body, errors, empty states — inside a design-method move or standalone.
modularize
Use when converting existing code to modular architecture (Laravel, Next.js, React). Triggers: "modularize", "convert to modules", "migrate to modular", "restructure modules".
research
Use when researching documentation, best practices, or complex technical investigations -- Context7 + Exa + Sequential Thinking methodology.
sniper-check
Use when validating code quality after modifications. Runs sniper agent in isolated forked context for clean, fast validation.
agent-creator
Use when creating expert agents. Generates agent.md with frontmatter, hooks, required sections, and skill references.
brainstorming
Use when creating a feature/component or adding functionality. Fires BEFORE APEX Analyze to refine requirements via structured questioning.
skill-creator
Use when creating new skills, restructuring existing skills, or improving skill documentation.
astro-7
Use when building Astro 7 sites, choosing an output mode (static/server/hybrid), configuring middleware, or upgrading from Astro 5/6.
astro-actions
Use when handling form submissions, mutations, or server-side logic with type safety in Astro via defineAction / astro:actions.
astro-assets
Use when optimizing images or other assets in Astro — <Image />, <Picture />, getImage(), Fonts API, or OG image generation.
astro-content
Use when managing structured content, blog posts, or typed data collections in Astro via the Content Layer API (content.config.ts).
astro-db
Use when doing database operations in an Astro project via Astro DB (defineDb, defineTable, db/config.ts, Turso).
astro-deployment
Use when deploying an Astro 7 app to Cloudflare, Vercel, Netlify, or Node.js — adapter setup, ISR patterns, edge middleware.
astro-i18n
Use when implementing i18n in Astro — locale routing strategies, getRelativeLocaleUrl/getAbsoluteLocaleUrl, Astro.currentLocale, or hreflang with sitemap.
astro-integrations
Use when adding React, Vue, Svelte, Solid, Preact, or another UI framework to an Astro project via @astrojs/* integrations.
astro-islands
Use when adding interactivity to Astro pages via client:* directives or rendering dynamic server content with server:defer.
astro-security
Use when configuring Content Security Policy (CSP) in Astro 7 — security headers, script/style hashes, nonces, or experimentalStaticHeaders.
astro-seo
Use when optimizing SEO for an Astro site — meta tags, Open Graph, JSON-LD structured data, sitemap/RSS, canonical URLs, hreflang, Core Web Vitals.
astro-starlight
Use when building a documentation site with Astro Starlight — sidebar config, Pagefind search, plugins (blog/openapi/typedoc), i18n, llms.txt.
astro-styling
Use when styling Astro components — scoped CSS, CSS Modules, Tailwind CSS, UnoCSS, Sass, the class:list directive, or global styles.
solid-astro
Use when applying SOLID principles to an Astro project — file-size limits, src/interfaces/ for types, JSDoc, modular structure, DRY.
go-concurrency
Use when writing or reviewing Go concurrency — goroutines, channels, errgroup, context cancellation, or goroutine leaks. Not for sequential idioms (go-core-idioms).
pr-summary
Summarize current pull request with diff, comments, and changed files. Use when reviewing PRs or before merging.
code-quality
Use when validating code quality after modifications -- SOLID compliance, DRY duplication, linter errors, architecture violations. Do NOT use for functional verification (run verification FIRST, then code-quality).
fuse-browser-usage
Use when about to call any mcp__fuse-browser__* tool. Routes fetch/crawl/SERP vs live browser session vs screenshot capture, and enforces the 4 ZERO-TOLERANCE rules -- read BEFORE the tool call.
react-effects-audit
Use when auditing React or Next.js components for unnecessary or unsafe useEffect usage -- detects 9 anti-patterns from "You Might Not Need an Effect".
tdd
Use when writing production code that needs tests -- new features, bug fixes, refactoring. Enforces RED-GREEN-REFACTOR before implementation.
commit-detection
Detects optimal commit type from git changes. Use when analyzing commits, determining commit type, or before committing.
git-flow
Use when committing, branching, opening PRs, or deciding merge/branch strategy.
post-commit
Use when a code commit just landed (not wip/amend/undo) and CHANGELOG or plugin-version post-commit actions are needed.
changelog-scan
Use when checking for new Claude Code versions, features, or changes since the last known release.
map-ecosystem
Use when cartography index descriptions are truncated, a new plugin/skill was just added, or after SessionStart regenerates the map.
breaking-changes
Use when checking whether a Claude Code update breaks our plugin ecosystem — hooks, agent frontmatter, manifest schema, or skill format.
community-pulse
Use when gauging community sentiment, bug reports, or feature requests about Claude Code via Exa search.
challenge
Use before a root-cause, done/verified claim, irreversible action, or 2nd-time fix reaches the owner (APEX or plain conversation); also fires at every eLicit/Verify gate. Not for code correctness (use sniper).
verification
Use when marking a task complete, finishing a feature, or claiming a bug fixed -- verifies functional resolution before closing. Do NOT use for lint/quality checks (use sniper AFTER this).
go-architecture
Use when laying out a new Go service, choosing an HTTP router or DB layer, or wiring dependencies. Not for concurrency (go-concurrency) or language idioms (go-core-idioms).
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.