菜单
Define architecture for a Sage/Acorn feature — architecture decision records, component boundaries, data flow, dependency mapping, pre-implementation design, trade-off analysis, Acorn architecture patterns, ADR, design before building
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Creates custom WordPress Abilities for the WP MCP Adapter (WP 6.9+). An Ability is a PHP class extending Roots\AcornAi\Abilities\Ability that exposes a JSON schema and execute() method — auto-discovered by the MCP Adapter and callable via Claude's execute-ability tool. Covers: lando wp acorn make:ability, AbilitiesServiceProvider registration, JSON schema definition, discover-abilities validation. Invoke for: abilities, make ability, custom mcp endpoint, discover-abilities, execute-ability, acorn ability, abilities-authoring, mcp endpoint, wp ability, make:ability.
Acorn CLI commands for WordPress automation — lando acorn make:command, artisan-style commands, Command::class, $signature, $description, handle() method, command arguments and options, output formatting, dependency injection in commands, calling other commands, AppServiceProvider registration, wp acorn schedule:run, scheduled commands, data import scripts, maintenance commands, theme automation tasks, lando acorn list
Eloquent, model, migration, relationship, hasMany, belongsTo, belongsToMany, Acorn Eloquent, custom table, wp_posts, wp_users, wp_postmeta, factory, query scope, scopePublished, global scope, make:model, make:migration, lando acorn migrate, $fillable, $casts, $timestamps, $primaryKey, HasFactory, db:seed, seeder — Eloquent ORM for custom and WordPress tables via Acorn
Livewire v3 in WordPress via Acorn: Livewire component, wire:model, wire:model.live, @livewire directive, reactive component, livewire component, make:livewire, Alpine + Livewire, wire:click, wire:submit, WithFileUploads, computed properties, mount lifecycle, hydrate, Acorn Livewire, roots/acorn-livewire, real-time UI, reactive forms — interactive server-driven UI without writing JavaScript in Sage themes
Logging in Acorn/WordPress — Log::debug(), Log::error(), Log::channel(), custom log channels, daily log files, stack channel, Slack log notifications, exception handling logging, WordPress debug.log integration, WP_DEBUG_LOG, structured logging, context arrays, monolog handlers, log levels, emergency info warning error debug, lando logs, lando ssh tail log
HTTP middleware, JWT authentication, auth middleware, custom guards, JWT guard, route middleware, request filter, middleware group, Acorn middleware, guard, rate limiting, CORS, CheckRole, throttle, bearer token, request filtering, middleware registration, HTTP Kernel — using Acorn's Laravel middleware stack inside WordPress/Sage/Bedrock
| name | superpowers-sage:architecting |
| description | Define architecture for a Sage/Acorn feature — architecture decision records, component boundaries, data flow, dependency mapping, pre-implementation design, trade-off analysis, Acorn architecture patterns, ADR, design before building |
| user-invocable | true |
| argument-hint | [feature or scope description] |
This skill remains available to avoid breaking existing workflows. It now orchestrates the new split flow:
superpowers-sage:architecture-discoverysuperpowers-sage:plan-generatorAnnounce at start: "I'm using architecting compatibility mode and will run architecture-discovery then plan-generator."
$ARGUMENTS
Do not implement code in this skill. If implementation is requested, complete the split planning flow first.
Before starting architecture discovery, check whether the visual foundation exists:
resources/css/design-tokens.css exist and contain real tokens (not a placeholder)?resources/views/kitchensink.blade.php or /kitchensink is accessible)?If both are present: proceed to Step 1 normally.
If either is missing or unvalidated:
⚠ Design system foundation not found.
Architecture for multi-block features should follow a validated design system.
Tokens, UI atoms, and layout components must exist before defining block schemas.
Recommendation: run /sage-design-system first.
→ It will create design-tokens.css, ui/ + layout/ Blade components, and validate with a kitchensink page.
→ Return to /architecting after the kitchensink screenshot is confirmed.
Proceed anyway? (only if this feature has no visual blocks / is purely backend)
Wait for explicit user confirmation before skipping the design system gate.
superpowers-sage:architecture-discovery with the same arguments.superpowers-sage:plan-generator with the approved spec path.After plan generation, offer:
subagent-driven-development for parallel task execution in this sessionsuperpowers-sage:building for direct implementation from plan filesdocs/superpowers/specs/YYYY-MM-DD-<topic>-architecture.mddocs/plans/YYYY-MM-DD-<topic>/plan.mdsuperpowers-sage:plan-generator.superpowers-sage:architecture-discovery review loop.superpowers-sage:plan-generator.