aurelius
Aurelius, the PMDS multi-framework app development framework for Claude Code.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 21 Nov 2026. Its scripts were only partly scanned.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/PMDevSolutions/Aurelius with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/PMDevSolutions/Aurelius'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/pmdevsolutions--aurelius)HTML
<a href="/listings/pmdevsolutions--aurelius"><img src="/api/listings/pmdevsolutions--aurelius/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
# Clone the repository git clone <repository-url> cd aurelius # Initialize a new project (Next.js, Vite, Astro, SvelteKit, or Expo) ./scripts/setup-project.sh my-app --vite # or --next, --astro, --svelte, --expo # Install dependencies cd my-app && pnpm install # Start development pnpm dev
**Video walkthrough:** [Aurelius: Clone to a Tested React App with Claude Code](https://youtu.be/Harcm6cYVpo) (3:46) follows these steps, then runs the four quality checks and one `/build-from-screenshot` pipeline.
Build from Figma (Autonomous Pipeline)
/build-from-figma https://figma.com/file/abc123/My-Design
This runs a 10-phase autonomous pipeline:
[0] Token Sync → Drift check (conditional, if lockfile exists) [1] Intake → Figma discovery + build-spec.json [2] Token Lock → Design tokens lockfile + Tailwind config [3] TDD (Gate) → Failing tests written first (mandatory) [4] Build → React components that pass the tests [5] Visual Diff → Pixel-level comparison loop (max 5 iterations, 2% threshold) [6] E2E Tests → Playwright tests (app-type-aware) [7] Cross-Browser→ Firefox/WebKit screenshots (non-blocking) [8] Quality Gate → Coverage + TypeScript + build + tokens + Lighthouse + mutation score (opt-in) [8.5] Responsive → Screenshots at 5 breakpoints (non-blocking) [9] Report → Build report with diff images + component docs
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
.claude-plugin/marketplace.json · Manifest · 18 lines
- {
- "$schema": "https://json.schemastore.org/claude-code-marketplace.json",
- "name": "aurelius",
- "description": "Aurelius, the PMDS multi-framework app development framework for Claude Code.",
- "owner": {
- "name": "Paul Mulligan",
- "url": "https://pmds.info"
- },
- "plugins": [
- {
- "name": "aurelius",
- "source": "./",
- "description": "Specialist agents, design-to-code pipelines with enforced TDD, a token lockfile and pixel-diff visual QA, and a deploy guard.",
- "category": "development",
- "tags": ["react", "design-to-code", "tdd", "visual-qa", "tailwind"]
- }
- ]
- }
README.md · README · 404 lines
- # Aurelius
- [](https://www.patreon.com/PaulMakesThings?utm_source=github)
- A Claude Code-integrated multi-framework app development framework with TypeScript, Tailwind CSS, and automated design-to-code pipelines.
- ## What This Framework Provides
- - **56 Custom Agents** -- Specialized AI agents for engineering, design, testing, marketing, operations, and more
- - **32 Development Skills** -- Automated workflows for Figma/Canva/screenshot/conversation conversion, TDD, E2E testing, visual QA, Storybook generation, state management, forms, auth, animation, SEO, and more
- - **10-Phase Design-to-React Pipeline** -- Convert Figma or Canva designs into fully working, tested React apps with a single command -- or just describe the app and let `/build-from-conversation` generate the Figma design first
- - **App-Type Awareness** -- Tailored build and test strategies for web apps, Chrome extensions, and PWAs
- - **Testing Stack** -- Vitest, React Testing Library, Playwright (cross-browser), Storybook, and pixel-diff visual QA
- - **Code Quality Scripts** -- Linting, formatting, type checking, bundle analysis, accessibility scanning, and design token verification
- - **Guard Rails** -- Claude Code hooks that stop deploys, publishes and releases for a human, deny commits that hardcode design values, and report a pipeline run in flight at session start
- - **Installable as a Plugin** -- other repos get the agents, knowledge skills and deploy guard with `/plugin install aurelius --marketplace PMDevSolutions/Aurelius`
- ## Quick Start
- ```bash
- # Clone the repository
- git clone <repository-url>
- cd aurelius
- # Initialize a new project (Next.js, Vite, Astro, SvelteKit, or Expo)
- ./scripts/setup-project.sh my-app --vite # or --next, --astro, --svelte, --expo
- # Install dependencies
- cd my-app && pnpm install
- # Start development
- pnpm dev
- ```
- **Video walkthrough:** [Aurelius: Clone to a Tested React App with Claude Code](https://youtu.be/Harcm6cYVpo) (3:46) follows these steps, then runs the four quality checks and one `/build-from-screenshot` pipeline.
- ### Build from Figma (Autonomous Pipeline)
- ```
- /build-from-figma https://figma.com/file/abc123/My-Design
- ```
- This runs a 10-phase autonomous pipeline:
- ```
- [0] Token Sync → Drift check (conditional, if lockfile exists)
- [1] Intake → Figma discovery + build-spec.json
- [2] Token Lock → Design tokens lockfile + Tailwind config
- [3] TDD (Gate) → Failing tests written first (mandatory)
- [4] Build → React components that pass the tests
- [5] Visual Diff → Pixel-level comparison loop (max 5 iterations, 2% threshold)
- [6] E2E Tests → Playwright tests (app-type-aware)
- [7] Cross-Browser→ Firefox/WebKit screenshots (non-blocking)
- [8] Quality Gate → Coverage + TypeScript + build + tokens + Lighthouse + mutation score (opt-in)
- [8.5] Responsive → Screenshots at 5 breakpoints (non-blocking)
- [9] Report → Build report with diff images + component docs
- ```
- ## Directory Structure
- ```
- project-root/
- ├── app/ # Your application (generated by pipeline or setup script)
- ├── scripts/ # Automation scripts
- │ ├── setup-project.sh # Initialize new project
- │ ├── lint-and-format.sh # ESLint + Prettier
- │ ├── run-tests.sh # Vitest with coverage
- │ ├── check-types.sh # TypeScript type checking
- │ ├── check-bundle-size.sh # Bundle size analysis
- │ ├── check-accessibility.sh # a11y scanning
- │ ├── verify-tokens.sh # Design token enforcement
- │ ├── verify-test-coverage.sh # Component test verification
- │ ├── visual-diff.js # Pixel-level screenshot comparison
- │ ├── cross-browser-test.sh # Playwright multi-browser (ad-hoc capture)
- │ ├── cross-browser-baseline.sh # Cross-browser baselines + provenance (RFC 0002)
- │ ├── setup-baseline-lfs.sh # Git LFS opt-in for large baseline sets
- │ ├── setup-playwright.sh # One-time browser setup
- │ ├── check-dead-code.sh # Dead code detection (knip)
- │ ├── check-security.sh # Dependency audit + anti-patterns
- │ ├── generate-api-client.sh # OpenAPI → typed client
- │ ├── check-responsive.sh # Responsive screenshots
- │ ├── check-dark-mode.sh # Dark mode verification
- │ ├── sync-tokens.sh # Token drift detection
- │ ├── generate-stories.sh # Storybook story generation
- │ └── generate-component-docs.sh # Component documentation
- ├── templates/ # Starter configs
- │ ├── shared/ # ESLint, Prettier, Tailwind, TS, Vitest
- │ ├── nextjs/ # Next.js config
- │ ├── vite/ # Vite config
- │ ├── astro/ # Astro hybrid-islands starter (React + Tailwind)
- │ └── chrome-extension/ # Playwright E2E fixtures for extensions
- ├── docs/ # Documentation
- │ ├── figma-to-react/ # Figma pipeline guide
- │ ├── canva-to-react/ # Canva pipeline guide
- │ └── react-development/ # Development standards
- ├── .claude/ # Claude Code configuration
- │ ├── agents/ # 56 custom agents
- │ ├── skills/ # 32 skills; each is also a slash command (/build-from-figma, /lint, /test)
- │ ├── hooks/ # Deploy guard, token guard, reminders, session status (stdin JSON hooks)
- │ ├── rules/ # Path-scoped standards (app code, pipeline artifacts, scripts, Claude Code)
- │ ├── workflows/ # component-lanes.js: build and visual-diff lanes per component
- │ ├── pipeline.config.json # Pipeline thresholds and app-type definitions
- │ ├── CUSTOM-AGENTS-GUIDE.md # Agent catalog
- │ └── PLUGINS-REFERENCE.md # Plugin reference
- ├── .claude-plugin/ # Packages the repo as the `aurelius` Claude Code plugin
- ├── evals/ # claude plugin eval cases for the framework's hard rules
- ├── CLAUDE.md # Claude Code project instructions
- └── README.md # This file
- ```
- ### Build from Canva (Autonomous Pipeline)
- ```
- /build-from-canva https://www.canva.com/design/DAGxyz.../My-Design
- ```
- Same 12-phase pipeline as Figma, with AI-powered token inference:
- - Phase 1: Vision-based design discovery (screenshots + Claude analysis)
- - Phase 2: AI token extraction with confidence scoring (requires user confirmation)
- - Phases 3-9: Shared pipeline (TDD, build, visual diff, E2E, quality gate)
- ### Build from Conversation (Autonomous Pipeline)
- ```
- /build-from-conversation a minimal analytics dashboard with auth and dark mode
- ```
- No design file needed -- describe the app and the pipeline designs it first:
- - Phase C0: Structured interview (max 7 questions) → `build-spec.json` + `design-brief.json`
- - Phase C1: The conversation-designer agent renders the brief as HTML mockups, which are captured into a **real Figma file** via the Figma MCP (`generate_figma_design`)
- - Handoff: The generated Figma URL feeds `/build-from-figma`, which runs unchanged (figma-intake fast-paths the interview)
- ### Build from InDesign (IDML / PDF)
- ```
- aurelius pipeline indesign brochure.pdf --target react --styling tailwind --output ./src/indesign
- ```
- For print-first sources, InDesign joins Figma and Canva as a first-class input. An
- exported **IDML** package or **PDF** (the normal designer handoff) is parsed into the
- shared IR, mapped to design tokens, and turned into typed React components plus
- Storybook stories — driven by the `indesign-to-react` agent or the
- `indesign-conversion` skill. See [`docs/pipelines/indesign.md`](docs/pipelines/indesign.md).
- ## Desktop GUI (experimental)
- Prefer not to use a terminal? A cross-platform **desktop GUI** wraps the workflow behind four screens: **Prerequisites**, **Setup wizard**, **Build from Figma**, and **Visual QA**. It's a thin orchestration layer over the existing scripts and Claude Code — the same pattern as Flavian's and Vespasian's GUIs. Download an installer for macOS, Windows or Linux from the [Releases page](https://github.com/PMDevSolutions/Aurelius/releases) (v2.1.0 onward), run it from source with `pnpm gui:dev`, or build an installer yourself with `pnpm gui:package`. See **[docs/GUI.md](docs/GUI.md)**.
- ## The Figma-to-React Pipeline
- ### How It Works
- The `/build-from-figma` command takes a Figma URL and autonomously builds a working React application through 10 phases. Key enforcement rules:
- - **TDD is mandatory** -- Tests are written before components (Phase 3 gates Phase 4)
- - **Visual QA uses pixel diff** -- `pixelmatch`-based comparison, not manual eyeballing
- - **E2E tests are generated** -- Tailored to app type (web app, Chrome extension, PWA)
- - **Design tokens are locked** -- A lockfile prevents hardcoded values from entering components
- ### Supported App Types
- | App Type | Detection | E2E Strategy | Special Handling |
- |----------|-----------|-------------|-----------------|
- | **Web App** | Default | Page navigation, forms, responsive | Standard Playwright |
- | **Chrome Extension** | `manifest.json` with `manifest_version` | Extension load, popup, storage, content scripts | Persistent browser context with `--load-extension` |
- | **PWA** | `manifest.json` with `start_url` | Install prompt, offline fallback | Service worker and offline tests |
- ### Pipeline Configuration
- All thresholds and behavior are configurable in `.claude/pipeline.config.json`:
- - Visual diff pass threshold (default: 2%)
- - Max visual iterations (default: 5)
- - TDD enforcement (default: on, non-negotiable)
- - Coverage threshold (default: 80%)
- - Lighthouse minimums (performance: 80, accessibility: 90)
- - App-type-specific E2E strategies
- ## 56 Custom Agents
- Claude Code delegates to an agent when your request matches its description, and may handle a small task itself instead. Naming the agent makes the delegation certain ("Use the test-writer-fixer agent to write tests for Checklist"):
- | Category | Count | Key Agents |
- |----------|-------|------------|
- | Engineering | 12 | frontend-developer, backend-architect, rapid-prototyper, test-writer-fixer, error-boundary-architect, migration-specialist, i18n-engineer, animation-optimizer, bundle-analyzer |
- | Design | 5 | ui-designer, ux-researcher, brand-guardian |
- | Design-to-Code | 8 | figma-react-converter, canva-react-converter, astro-converter, vue-converter, svelte-converter, react-native-converter, conversation-designer, asset-cataloger |
- | Testing & QA | 7 | visual-qa-agent, accessibility-auditor, api-tester, performance-benchmarker |
- | Product | 3 | sprint-prioritizer, feedback-synthesizer, trend-researcher |
- | Marketing | 7 | content-creator, growth-hacker, app-store-optimizer |
- | Project Mgmt | 3 | studio-producer, project-shipper, experiment-tracker |
- | Operations | 5 | analytics-reporter, infrastructure-maintainer, legal-compliance-checker |
- | Other | 5 | docusaurus-expert, agent-expert, command-expert, joker, studio-coach |
- Full catalog: `.claude/CUSTOM-AGENTS-GUIDE.md`
- ## 32 Development Skills
- ### Pipeline Skills
- | # | Skill | Purpose |
- |---|-------|---------|
- | 1 | figma-intake | Figma discovery + build-spec.json generation |
- | 2 | design-token-lock | Extract and lock design tokens from Figma |
- | 3 | tdd-from-figma | Write failing tests before components (app-type-aware) |
- | 4 | figma-to-react-workflow | Generate components that pass the tests |
- | 5 | visual-qa-verification | Pixel-diff comparison loop with region analysis |
- | 6 | e2e-test-generator | Generate Playwright E2E tests (app-type-aware) |
- | 7 | parallel-orchestration | Concurrent phase execution with dependency graph |
- ### Canva, Screenshot & Conversation Pipeline Skills
- | # | Skill | Purpose |
- |---|-------|---------|
- | 8 | canva-intake | Canva design discovery + build-spec.json generation |
- | 9 | canva-token-inference | AI-powered token extraction from Canva/screenshot sources |
- | 10 | screenshot-intake | URL/screenshot capture + vision-based discovery |
- | 11 | conversation-intake | Conversational interview → build-spec.json + design-brief.json |
- | 12 | design-brief-to-figma | Generate a real Figma file from the design brief (HTML-mockup capture) |
- ### React Development Skills
- | # | Skill | Purpose |
- |---|-------|---------|
- | 13 | react-component-development | Component patterns, hooks, composition |
- | 14 | react-testing-workflows | Vitest, RTL, Playwright, Storybook |
- | 15 | react-performance-optimization | Profiling, bundle analysis, Web Vitals |
- | 16 | react-accessibility | WCAG 2.1 AA patterns for React |
- | 17 | state-management | Zustand, TanStack Query, URL state architecture |
- | 18 | form-handling | React Hook Form + Zod: typed forms, wizards |
- | 19 | auth-flows | Auth.js, Clerk, Supabase Auth, RBAC |
- | 20 | animation-motion | Framer Motion, CSS transitions, reduced-motion a11y |
- | 21 | seo-metadata | Next.js Metadata API, JSON-LD, OG images, sitemaps |
- ### Export Skills
- | # | Skill | Purpose |
- |---|-------|---------|
- | 22 | export-design-system | Export components + tokens as a publishable pnpm workspace |
- ### InDesign Skills
- | # | Skill | Purpose |
- |---|-------|---------|
- | 23 | indesign-conversion | Convert an InDesign IDML/PDF into React components, design tokens, and stories |
- ### Storybook Skills
- | # | Skill | Purpose |
- |---|-------|---------|
- | 24 | storybook-story-generation | Auto-generate Storybook stories + MDX docs from built components (Phase 4.5, non-blocking) |
- ### Pipeline and Quality Skills (slash commands)
- | # | Skill | Purpose |
- |---|-------|---------|
- | 25 | build-from-figma | `/build-from-figma <url>`: the full Figma-to-app pipeline |
- | 26 | build-from-canva | `/build-from-canva <url>`: the same pipeline from a Canva design |
- | 27 | build-from-screenshot | `/build-from-screenshot <url \| paths>`: from a live URL or images, any output target |
- | 28 | build-from-conversation | `/build-from-conversation [description]`: interview, generated Figma file, then the Figma pipeline |
- | 29 | verify-all | `/verify-all`: every local quality check with a summary |
- | 30 | ci | `/ci`: the same checks, JSON output, non-zero exit on failure |
- | 31 | lint | `/lint [--check]`: ESLint + Prettier |
- | 32 | test | `/test [file \| -t pattern] [--coverage]`: Vitest |
- Full catalog: `.claude/skills/README.md`
- ## Scripts
- ### Code Quality
- ```bash
- ./scripts/lint-and-format.sh # ESLint + Prettier
- ./scripts/check-types.sh # TypeScript type checking
- ./scripts/check-bundle-size.sh # Bundle size analysis
- ./scripts/check-accessibility.sh # Automated a11y scanning
- ```
- ### Testing
- ```bash
- ./scripts/run-tests.sh # Vitest unit/component tests
- ./scripts/cross-browser-test.sh # Playwright multi-browser screenshots (ad-hoc)
- ./scripts/cross-browser-baseline.sh # Cross-browser baseline capture/compare (RFC 0002)
- ./scripts/setup-baseline-lfs.sh # Route large baseline sets through Git LFS
- ./scripts/setup-playwright.sh # One-time browser engine setup
- ```
- ### Mutation testing (Stryker)
- Mutation testing measures how well the test suite actually catches bugs. The
- framework's own TypeScript code (`packages/pipeline`) is mutation-tested via
- [Stryker](https://stryker-mutator.io/); `stryker.conf.json` lives at the repo
- root but **runs from `packages/pipeline`** so the pnpm-linked dependencies resolve
- inside Stryker's sandbox.
- ```bash
- # Full run (slow — re-runs the suite per mutant)
- cd packages/pipeline && npx stryker run ../../stryker.conf.json
- # Scope to one area while iterating
- cd packages/pipeline && npx stryker run ../../stryker.conf.json --mutate "src/tokens/**/*.ts"
- ```
- The HTML report is written to `packages/pipeline/reports/mutation/index.html`.
- - **Threshold (opt-in).** The target mutation score lives in
- `.claude/pipeline.config.json` → `qualityGate.mutationScore`
- (`{ "enabled": false, "threshold": 80, "blocking": false }`). It is **off by
- default**; set `enabled: true` to treat it as a quality gate.
- - **CI.** `.github/workflows/mutation.yml` runs Stryker **nightly** and
- **on demand** (`workflow_dispatch`) — never on PRs, to avoid latency. It is
- informational: the score is posted to the run summary and the HTML report is
- uploaded as an artifact.
- ### Pipeline Verification
- ```bash
- ./scripts/verify-tokens.sh # Catch hardcoded design values
- ./scripts/verify-test-coverage.sh # Ensure every component has tests
- node scripts/visual-diff.js --batch actual/ expected/ --json # Pixel diff
- ```
- Full reference: `scripts/README.md`
- ## Templates
- Starter configuration files for new projects:
- | Directory | Contents |
- |-----------|----------|
- | `templates/shared/` | ESLint, Prettier, Tailwind, TypeScript, Vitest configs |
- | `templates/nextjs/` | Next.js config |
- | `templates/vite/` | Vite config |
- | `templates/astro/` | Astro hybrid-islands starter (React islands + Tailwind, file-based routing) |
- | `templates/chrome-extension/` | Playwright E2E fixtures for Chrome extensions |
- Full reference: `templates/README.md`
- ## MCP Server Integration
- The framework uses four MCP (Model Context Protocol) servers for Figma access, browser automation, and testing:
- | Server | Purpose | Required For |
- |--------|---------|-------------|
- | **Figma Desktop MCP** | Read designs, extract tokens, capture screenshots from Figma | Phases 1-2, 5 |
- | **Figma Remote MCP** | Fallback remote Figma access | Phases 1-2, 5 |
- | **Chrome DevTools MCP** | Screenshots, Lighthouse audits, DOM inspection | Phases 5, 7-8 |
- | **Canva AI Connector** | Search, export, interact with Canva designs | Phases 1-2 (Canva) |
- | **Playwright MCP** | Cross-browser testing (Chromium, Firefox, WebKit) | Phases 6-7 |
- MCP servers are configured in `.mcp.json` (Chrome DevTools MCP at user scope; see `.claude/PLUGINS-REFERENCE.md`). Figma Desktop MCP requires the Figma desktop app running locally.
- ## Claude Code Plugin
- Aurelius needs no plugin to run, and it is one: `.claude-plugin/plugin.json` packages the agents, skills, hooks and workflow. To use the agents and knowledge skills in another repo:
- ```
- /plugin install aurelius --marketplace PMDevSolutions/Aurelius
- ```
- The pipeline skills call this repo's `scripts/`, so they run only in an Aurelius checkout. Optional official plugins that fit (`typescript-lsp`, `commit-commands` for `/commit`) and the MCP servers the agents expect: `.claude/PLUGINS-REFERENCE.md`. GitHub integration is the `gh` CLI (not a plugin).
- ## Documentation Index
- | Document | Location | Description |
- |----------|----------|-------------|
- | **Developer onboarding** | `docs/onboarding/README.md` | Start here -- quickstart, architecture, configuration, troubleshooting |
- | Quickstart guide | `docs/onboarding/quickstart.md` | Clone to running project in 10 minutes |
- | Architecture overview | `docs/onboarding/architecture.md` | All 56 agents, 32 skills, 4 pipelines, and how they connect |
- | Pipeline configuration | `docs/onboarding/pipeline-configuration.md` | Every setting in pipeline.config.json explained |
- | Troubleshooting FAQ | `docs/onboarding/troubleshooting.md` | Common issues and solutions |
- | Project instructions | `CLAUDE.md` | Full project config for Claude Code |
- | Figma pipeline guide | `docs/figma-to-react/README.md` | Pipeline overview and troubleshooting |
- | React standards | `docs/react-development/README.md` | TypeScript, Tailwind, testing conventions |
- | Canva pipeline guide | `docs/canva-to-react/README.md` | Canva pipeline overview and troubleshooting |
- | Conversation pipeline guide | `docs/conversation-to-app/README.md` | Conversational app creation via generated Figma designs |
- | InDesign pipeline guide | `docs/pipelines/indesign.md` | Convert exported IDML/PDF into React components, tokens, and Storybook stories |
- | Design system export | `docs/design-system-export/consumers.md` | Export format, round-trip re-import, and how Flavian/Nerva consume the tokens |
- | Desktop GUI | `docs/GUI.md` | The experimental Electron GUI: screens, commands, packaging |
- | Agent catalog | `.claude/CUSTOM-AGENTS-GUIDE.md` | All 56 agents with use cases |
- | Skills catalog | `.claude/skills/README.md` | All 32 skills with triggers |
- | Plugin reference | `.claude/PLUGINS-REFERENCE.md` | Aurelius as a plugin, optional plugins, expected MCP servers |
- | Hook system | `docs/guides/hooks.md` | The deploy guard, commit guards and reminders, and how to write a hook |
- | Evals | `evals/README.md` | `claude plugin eval` cases for the framework's hard rules |
- | Scripts reference | `scripts/README.md` | All scripts with usage examples |
- | Templates reference | `templates/README.md` | Starter configs and how to use them |
- | Pipeline config | `.claude/pipeline.config.json` | Thresholds, app types, quality gates |
- | Agent naming guide | `.claude/AGENT-NAMING-GUIDE.md` | Conventions for creating new agents |
- ## Related Projects
- | Project | Description |
- |---------|-------------|
- | [AI SEO Copilot (Chrome)](https://github.com/die-Manufaktur/AISEOC-Chrome-Extension) | Free, open-source Chrome extension for AI-powered SEO analysis. Built with React 19, TypeScript, and Vite. The Chrome extension pipeline in Aurelius was battle-tested against this project. [Install from Chrome Web Store](https://chromewebstore.google.com/detail/ai-seo-copilot/anhpobnkbmgjhcgbohkddjjpcbbdllhl) |
- | [AI SEO Copilot (Webflow)](https://github.com/die-Manufaktur/AI-SEO-Copilot-for-Webflow) | The original Webflow app with ~20,000 installs |
- | [Flavian](https://github.com/PMDevSolutions/Flavian) | Claude Code-integrated WordPress development framework with FSE block theme tools and Figma-to-WordPress pipelines |
- | [Nerva](https://github.com/PMDevSolutions/Nerva) | Claude Code-integrated API and backend development framework with Hono, Cloudflare Workers, and Drizzle ORM |
- | [Claudius](https://github.com/PMDevSolutions/Claudius) | Embeddable AI chat widget powered by Claude. React + TypeScript + Cloudflare Workers |
- ## Credits
- These agents in `.claude/agents/` are based on the agent definitions in [contains-studio/agents](https://github.com/contains-studio/agents) by Contains Studio, adapted for this project: `ai-engineer`, `analytics-reporter`, `api-tester`, `app-store-optimizer`, `backend-architect`, `brand-guardian`, `content-creator`, `devops-automator`, `experiment-tracker`, `feedback-synthesizer`, `finance-tracker`, `frontend-developer`, `growth-hacker`, `infrastructure-maintainer`, `instagram-curator`, `joker`, `legal-compliance-checker`, `mobile-app-builder`, `performance-benchmarker`, `project-shipper`, `rapid-prototyper`, `reddit-community-builder`, `sprint-prioritizer`, `studio-coach`, `studio-producer`, `support-responder`, `test-results-analyzer`, `test-writer-fixer`, `tiktok-strategist`, `tool-evaluator`, `trend-researcher`, `twitter-engager`, `ui-designer`, `ux-researcher`, `visual-storyteller`, `whimsy-injector`, `workflow-optimizer`. Thanks to Contains Studio for sharing them.
- ## License
- MIT
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.