Arcana
Add arcana for ritual’s TDD-centric engineering pipelines plus imagine’s MCP-backed image generation for product and research work.
Overview
arcana is a plugin marketplace for the Build phase that bundles ritual TDD-orchestrated engineering workflows and imagine MCP image generation.
What is this marketplace?
- 2-plugin marketplace: ritual (v0.20.0) software workflow and imagine (v0.2.0) image generation
- ritual: triage, TDD, self-review, docs sync, autonomous orchestrators for feat/fix/refactor/docs
- imagine: provider-agnostic image gen with fal.ai default, Flux, and MCP integration
- Owner metadata spans software engineering, game development, and research domains
- Natural-language prompts enriched with project context for visual assets
- 2 plugins: ritual v0.20.0 and imagine v0.2.0
- ritual covers triage, TDD, self-review, docs sync, and four pipeline orchestrators
- imagine defaults to fal.ai with Flux over MCP
Community signal: 1 GitHub stars.
What problem does it solve?
Solo builders juggle ad-hoc agent threads for coding and separate tools for visuals, so triage, tests, and docs drift out of sync.
Who is it for?
Indie devs shipping products, small games, or research prototypes who want orchestrated engineering plus in-session imagery.
Skip if: Enterprises needing a large curated guard suite or teams that only want image generation without workflow discipline.
What do I get? / Deliverables
After you install arcana, ritual runs structured feat/fix/refactor/docs pipelines with TDD and docs sync, while imagine supplies fal-powered images from the same Claude Code session.
- Orchestrated feat/fix/refactor/docs runs via ritual
- Self-review and documentation sync checkpoints
- Generated images from enriched natural-language prompts
Plugins in this marketplace
2 plugins — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Build / pm is the shelf because ritual’s orchestrated feat/fix/refactor/docs workflows are the marketplace’s engineering anchor. Pm covers triage-through-delivery orchestration; testing and docs sync are explicit ritual phases rather than optional extras.
How it compares
Dual-plugin engineering ritual plus MCP art, not a verify-only guard pack or a docs-only lookup skill.
Common Questions / FAQ
Who is Arcana for?
It is for builders using Claude Code who want yanek’s ritual pipelines for TDD and orchestration plus imagine for fal.ai/Flux image generation in one marketplace.
When should I use Arcana?
Use ritual when starting feat/fix/refactor/docs work that needs triage, tests, and docs sync; use imagine when you need context-aware visuals during the same project.
How do I add Arcana to my agent?
Register market:yanekyuk/Arcana in Claude Code, enable ritual for workflow plugins and imagine for MCP image gen, and configure your active image provider (fal.ai by default).