Skip to content
Back to search

aurelius

MarketplaceWorks with Claude CodeGitHub

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.

Checked today

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
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/pmdevsolutions--aurelius/badge.svg)](/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
  1. {
  2. "$schema": "https://json.schemastore.org/claude-code-marketplace.json",
  3. "name": "aurelius",
  4. "description": "Aurelius, the PMDS multi-framework app development framework for Claude Code.",
  5. "owner": {
  6. "name": "Paul Mulligan",
  7. "url": "https://pmds.info"
  8. },
  9. "plugins": [
  10. {
  11. "name": "aurelius",
  12. "source": "./",
  13. "description": "Specialist agents, design-to-code pipelines with enforced TDD, a token lockfile and pixel-diff visual QA, and a deploy guard.",
  14. "category": "development",
  15. "tags": ["react", "design-to-code", "tdd", "visual-qa", "tailwind"]
  16. }
  17. ]
  18. }
README.md · README · 404 lines
  1. # Aurelius
  2. [![Patreon](https://img.shields.io/badge/Patreon-Support-orange?logo=patreon)](https://www.patreon.com/PaulMakesThings?utm_source=github)
  3. A Claude Code-integrated multi-framework app development framework with TypeScript, Tailwind CSS, and automated design-to-code pipelines.
  4. ## What This Framework Provides
  5. - **56 Custom Agents** -- Specialized AI agents for engineering, design, testing, marketing, operations, and more
  6. - **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
  7. - **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
  8. - **App-Type Awareness** -- Tailored build and test strategies for web apps, Chrome extensions, and PWAs
  9. - **Testing Stack** -- Vitest, React Testing Library, Playwright (cross-browser), Storybook, and pixel-diff visual QA
  10. - **Code Quality Scripts** -- Linting, formatting, type checking, bundle analysis, accessibility scanning, and design token verification
  11. - **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
  12. - **Installable as a Plugin** -- other repos get the agents, knowledge skills and deploy guard with `/plugin install aurelius --marketplace PMDevSolutions/Aurelius`
  13. ## Quick Start
  14. ```bash
  15. # Clone the repository
  16. git clone <repository-url>
  17. cd aurelius
  18. # Initialize a new project (Next.js, Vite, Astro, SvelteKit, or Expo)
  19. ./scripts/setup-project.sh my-app --vite # or --next, --astro, --svelte, --expo
  20. # Install dependencies
  21. cd my-app && pnpm install
  22. # Start development
  23. pnpm dev
  24. ```
  25. **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.
  26. ### Build from Figma (Autonomous Pipeline)
  27. ```
  28. /build-from-figma https://figma.com/file/abc123/My-Design
  29. ```
  30. This runs a 10-phase autonomous pipeline:
  31. ```
  32. [0] Token Sync → Drift check (conditional, if lockfile exists)
  33. [1] Intake → Figma discovery + build-spec.json
  34. [2] Token Lock → Design tokens lockfile + Tailwind config
  35. [3] TDD (Gate) → Failing tests written first (mandatory)
  36. [4] Build → React components that pass the tests
  37. [5] Visual Diff → Pixel-level comparison loop (max 5 iterations, 2% threshold)
  38. [6] E2E Tests → Playwright tests (app-type-aware)
  39. [7] Cross-Browser→ Firefox/WebKit screenshots (non-blocking)
  40. [8] Quality Gate → Coverage + TypeScript + build + tokens + Lighthouse + mutation score (opt-in)
  41. [8.5] Responsive → Screenshots at 5 breakpoints (non-blocking)
  42. [9] Report → Build report with diff images + component docs
  43. ```
  44. ## Directory Structure
  45. ```
  46. project-root/
  47. ├── app/ # Your application (generated by pipeline or setup script)
  48. ├── scripts/ # Automation scripts
  49. │ ├── setup-project.sh # Initialize new project
  50. │ ├── lint-and-format.sh # ESLint + Prettier
  51. │ ├── run-tests.sh # Vitest with coverage
  52. │ ├── check-types.sh # TypeScript type checking
  53. │ ├── check-bundle-size.sh # Bundle size analysis
  54. │ ├── check-accessibility.sh # a11y scanning
  55. │ ├── verify-tokens.sh # Design token enforcement
  56. │ ├── verify-test-coverage.sh # Component test verification
  57. │ ├── visual-diff.js # Pixel-level screenshot comparison
  58. │ ├── cross-browser-test.sh # Playwright multi-browser (ad-hoc capture)
  59. │ ├── cross-browser-baseline.sh # Cross-browser baselines + provenance (RFC 0002)
  60. │ ├── setup-baseline-lfs.sh # Git LFS opt-in for large baseline sets
  61. │ ├── setup-playwright.sh # One-time browser setup
  62. │ ├── check-dead-code.sh # Dead code detection (knip)
  63. │ ├── check-security.sh # Dependency audit + anti-patterns
  64. │ ├── generate-api-client.sh # OpenAPI → typed client
  65. │ ├── check-responsive.sh # Responsive screenshots
  66. │ ├── check-dark-mode.sh # Dark mode verification
  67. │ ├── sync-tokens.sh # Token drift detection
  68. │ ├── generate-stories.sh # Storybook story generation
  69. │ └── generate-component-docs.sh # Component documentation
  70. ├── templates/ # Starter configs
  71. │ ├── shared/ # ESLint, Prettier, Tailwind, TS, Vitest
  72. │ ├── nextjs/ # Next.js config
  73. │ ├── vite/ # Vite config
  74. │ ├── astro/ # Astro hybrid-islands starter (React + Tailwind)
  75. │ └── chrome-extension/ # Playwright E2E fixtures for extensions
  76. ├── docs/ # Documentation
  77. │ ├── figma-to-react/ # Figma pipeline guide
  78. │ ├── canva-to-react/ # Canva pipeline guide
  79. │ └── react-development/ # Development standards
  80. ├── .claude/ # Claude Code configuration
  81. │ ├── agents/ # 56 custom agents
  82. │ ├── skills/ # 32 skills; each is also a slash command (/build-from-figma, /lint, /test)
  83. │ ├── hooks/ # Deploy guard, token guard, reminders, session status (stdin JSON hooks)
  84. │ ├── rules/ # Path-scoped standards (app code, pipeline artifacts, scripts, Claude Code)
  85. │ ├── workflows/ # component-lanes.js: build and visual-diff lanes per component
  86. │ ├── pipeline.config.json # Pipeline thresholds and app-type definitions
  87. │ ├── CUSTOM-AGENTS-GUIDE.md # Agent catalog
  88. │ └── PLUGINS-REFERENCE.md # Plugin reference
  89. ├── .claude-plugin/ # Packages the repo as the `aurelius` Claude Code plugin
  90. ├── evals/ # claude plugin eval cases for the framework's hard rules
  91. ├── CLAUDE.md # Claude Code project instructions
  92. └── README.md # This file
  93. ```
  94. ### Build from Canva (Autonomous Pipeline)
  95. ```
  96. /build-from-canva https://www.canva.com/design/DAGxyz.../My-Design
  97. ```
  98. Same 12-phase pipeline as Figma, with AI-powered token inference:
  99. - Phase 1: Vision-based design discovery (screenshots + Claude analysis)
  100. - Phase 2: AI token extraction with confidence scoring (requires user confirmation)
  101. - Phases 3-9: Shared pipeline (TDD, build, visual diff, E2E, quality gate)
  102. ### Build from Conversation (Autonomous Pipeline)
  103. ```
  104. /build-from-conversation a minimal analytics dashboard with auth and dark mode
  105. ```
  106. No design file needed -- describe the app and the pipeline designs it first:
  107. - Phase C0: Structured interview (max 7 questions) → `build-spec.json` + `design-brief.json`
  108. - 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`)
  109. - Handoff: The generated Figma URL feeds `/build-from-figma`, which runs unchanged (figma-intake fast-paths the interview)
  110. ### Build from InDesign (IDML / PDF)
  111. ```
  112. aurelius pipeline indesign brochure.pdf --target react --styling tailwind --output ./src/indesign
  113. ```
  114. For print-first sources, InDesign joins Figma and Canva as a first-class input. An
  115. exported **IDML** package or **PDF** (the normal designer handoff) is parsed into the
  116. shared IR, mapped to design tokens, and turned into typed React components plus
  117. Storybook stories — driven by the `indesign-to-react` agent or the
  118. `indesign-conversion` skill. See [`docs/pipelines/indesign.md`](docs/pipelines/indesign.md).
  119. ## Desktop GUI (experimental)
  120. 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)**.
  121. ## The Figma-to-React Pipeline
  122. ### How It Works
  123. The `/build-from-figma` command takes a Figma URL and autonomously builds a working React application through 10 phases. Key enforcement rules:
  124. - **TDD is mandatory** -- Tests are written before components (Phase 3 gates Phase 4)
  125. - **Visual QA uses pixel diff** -- `pixelmatch`-based comparison, not manual eyeballing
  126. - **E2E tests are generated** -- Tailored to app type (web app, Chrome extension, PWA)
  127. - **Design tokens are locked** -- A lockfile prevents hardcoded values from entering components
  128. ### Supported App Types
  129. | App Type | Detection | E2E Strategy | Special Handling |
  130. |----------|-----------|-------------|-----------------|
  131. | **Web App** | Default | Page navigation, forms, responsive | Standard Playwright |
  132. | **Chrome Extension** | `manifest.json` with `manifest_version` | Extension load, popup, storage, content scripts | Persistent browser context with `--load-extension` |
  133. | **PWA** | `manifest.json` with `start_url` | Install prompt, offline fallback | Service worker and offline tests |
  134. ### Pipeline Configuration
  135. All thresholds and behavior are configurable in `.claude/pipeline.config.json`:
  136. - Visual diff pass threshold (default: 2%)
  137. - Max visual iterations (default: 5)
  138. - TDD enforcement (default: on, non-negotiable)
  139. - Coverage threshold (default: 80%)
  140. - Lighthouse minimums (performance: 80, accessibility: 90)
  141. - App-type-specific E2E strategies
  142. ## 56 Custom Agents
  143. 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"):
  144. | Category | Count | Key Agents |
  145. |----------|-------|------------|
  146. | Engineering | 12 | frontend-developer, backend-architect, rapid-prototyper, test-writer-fixer, error-boundary-architect, migration-specialist, i18n-engineer, animation-optimizer, bundle-analyzer |
  147. | Design | 5 | ui-designer, ux-researcher, brand-guardian |
  148. | Design-to-Code | 8 | figma-react-converter, canva-react-converter, astro-converter, vue-converter, svelte-converter, react-native-converter, conversation-designer, asset-cataloger |
  149. | Testing & QA | 7 | visual-qa-agent, accessibility-auditor, api-tester, performance-benchmarker |
  150. | Product | 3 | sprint-prioritizer, feedback-synthesizer, trend-researcher |
  151. | Marketing | 7 | content-creator, growth-hacker, app-store-optimizer |
  152. | Project Mgmt | 3 | studio-producer, project-shipper, experiment-tracker |
  153. | Operations | 5 | analytics-reporter, infrastructure-maintainer, legal-compliance-checker |
  154. | Other | 5 | docusaurus-expert, agent-expert, command-expert, joker, studio-coach |
  155. Full catalog: `.claude/CUSTOM-AGENTS-GUIDE.md`
  156. ## 32 Development Skills
  157. ### Pipeline Skills
  158. | # | Skill | Purpose |
  159. |---|-------|---------|
  160. | 1 | figma-intake | Figma discovery + build-spec.json generation |
  161. | 2 | design-token-lock | Extract and lock design tokens from Figma |
  162. | 3 | tdd-from-figma | Write failing tests before components (app-type-aware) |
  163. | 4 | figma-to-react-workflow | Generate components that pass the tests |
  164. | 5 | visual-qa-verification | Pixel-diff comparison loop with region analysis |
  165. | 6 | e2e-test-generator | Generate Playwright E2E tests (app-type-aware) |
  166. | 7 | parallel-orchestration | Concurrent phase execution with dependency graph |
  167. ### Canva, Screenshot & Conversation Pipeline Skills
  168. | # | Skill | Purpose |
  169. |---|-------|---------|
  170. | 8 | canva-intake | Canva design discovery + build-spec.json generation |
  171. | 9 | canva-token-inference | AI-powered token extraction from Canva/screenshot sources |
  172. | 10 | screenshot-intake | URL/screenshot capture + vision-based discovery |
  173. | 11 | conversation-intake | Conversational interview → build-spec.json + design-brief.json |
  174. | 12 | design-brief-to-figma | Generate a real Figma file from the design brief (HTML-mockup capture) |
  175. ### React Development Skills
  176. | # | Skill | Purpose |
  177. |---|-------|---------|
  178. | 13 | react-component-development | Component patterns, hooks, composition |
  179. | 14 | react-testing-workflows | Vitest, RTL, Playwright, Storybook |
  180. | 15 | react-performance-optimization | Profiling, bundle analysis, Web Vitals |
  181. | 16 | react-accessibility | WCAG 2.1 AA patterns for React |
  182. | 17 | state-management | Zustand, TanStack Query, URL state architecture |
  183. | 18 | form-handling | React Hook Form + Zod: typed forms, wizards |
  184. | 19 | auth-flows | Auth.js, Clerk, Supabase Auth, RBAC |
  185. | 20 | animation-motion | Framer Motion, CSS transitions, reduced-motion a11y |
  186. | 21 | seo-metadata | Next.js Metadata API, JSON-LD, OG images, sitemaps |
  187. ### Export Skills
  188. | # | Skill | Purpose |
  189. |---|-------|---------|
  190. | 22 | export-design-system | Export components + tokens as a publishable pnpm workspace |
  191. ### InDesign Skills
  192. | # | Skill | Purpose |
  193. |---|-------|---------|
  194. | 23 | indesign-conversion | Convert an InDesign IDML/PDF into React components, design tokens, and stories |
  195. ### Storybook Skills
  196. | # | Skill | Purpose |
  197. |---|-------|---------|
  198. | 24 | storybook-story-generation | Auto-generate Storybook stories + MDX docs from built components (Phase 4.5, non-blocking) |
  199. ### Pipeline and Quality Skills (slash commands)
  200. | # | Skill | Purpose |
  201. |---|-------|---------|
  202. | 25 | build-from-figma | `/build-from-figma <url>`: the full Figma-to-app pipeline |
  203. | 26 | build-from-canva | `/build-from-canva <url>`: the same pipeline from a Canva design |
  204. | 27 | build-from-screenshot | `/build-from-screenshot <url \| paths>`: from a live URL or images, any output target |
  205. | 28 | build-from-conversation | `/build-from-conversation [description]`: interview, generated Figma file, then the Figma pipeline |
  206. | 29 | verify-all | `/verify-all`: every local quality check with a summary |
  207. | 30 | ci | `/ci`: the same checks, JSON output, non-zero exit on failure |
  208. | 31 | lint | `/lint [--check]`: ESLint + Prettier |
  209. | 32 | test | `/test [file \| -t pattern] [--coverage]`: Vitest |
  210. Full catalog: `.claude/skills/README.md`
  211. ## Scripts
  212. ### Code Quality
  213. ```bash
  214. ./scripts/lint-and-format.sh # ESLint + Prettier
  215. ./scripts/check-types.sh # TypeScript type checking
  216. ./scripts/check-bundle-size.sh # Bundle size analysis
  217. ./scripts/check-accessibility.sh # Automated a11y scanning
  218. ```
  219. ### Testing
  220. ```bash
  221. ./scripts/run-tests.sh # Vitest unit/component tests
  222. ./scripts/cross-browser-test.sh # Playwright multi-browser screenshots (ad-hoc)
  223. ./scripts/cross-browser-baseline.sh # Cross-browser baseline capture/compare (RFC 0002)
  224. ./scripts/setup-baseline-lfs.sh # Route large baseline sets through Git LFS
  225. ./scripts/setup-playwright.sh # One-time browser engine setup
  226. ```
  227. ### Mutation testing (Stryker)
  228. Mutation testing measures how well the test suite actually catches bugs. The
  229. framework's own TypeScript code (`packages/pipeline`) is mutation-tested via
  230. [Stryker](https://stryker-mutator.io/); `stryker.conf.json` lives at the repo
  231. root but **runs from `packages/pipeline`** so the pnpm-linked dependencies resolve
  232. inside Stryker's sandbox.
  233. ```bash
  234. # Full run (slow — re-runs the suite per mutant)
  235. cd packages/pipeline && npx stryker run ../../stryker.conf.json
  236. # Scope to one area while iterating
  237. cd packages/pipeline && npx stryker run ../../stryker.conf.json --mutate "src/tokens/**/*.ts"
  238. ```
  239. The HTML report is written to `packages/pipeline/reports/mutation/index.html`.
  240. - **Threshold (opt-in).** The target mutation score lives in
  241. `.claude/pipeline.config.json` → `qualityGate.mutationScore`
  242. (`{ "enabled": false, "threshold": 80, "blocking": false }`). It is **off by
  243. default**; set `enabled: true` to treat it as a quality gate.
  244. - **CI.** `.github/workflows/mutation.yml` runs Stryker **nightly** and
  245. **on demand** (`workflow_dispatch`) — never on PRs, to avoid latency. It is
  246. informational: the score is posted to the run summary and the HTML report is
  247. uploaded as an artifact.
  248. ### Pipeline Verification
  249. ```bash
  250. ./scripts/verify-tokens.sh # Catch hardcoded design values
  251. ./scripts/verify-test-coverage.sh # Ensure every component has tests
  252. node scripts/visual-diff.js --batch actual/ expected/ --json # Pixel diff
  253. ```
  254. Full reference: `scripts/README.md`
  255. ## Templates
  256. Starter configuration files for new projects:
  257. | Directory | Contents |
  258. |-----------|----------|
  259. | `templates/shared/` | ESLint, Prettier, Tailwind, TypeScript, Vitest configs |
  260. | `templates/nextjs/` | Next.js config |
  261. | `templates/vite/` | Vite config |
  262. | `templates/astro/` | Astro hybrid-islands starter (React islands + Tailwind, file-based routing) |
  263. | `templates/chrome-extension/` | Playwright E2E fixtures for Chrome extensions |
  264. Full reference: `templates/README.md`
  265. ## MCP Server Integration
  266. The framework uses four MCP (Model Context Protocol) servers for Figma access, browser automation, and testing:
  267. | Server | Purpose | Required For |
  268. |--------|---------|-------------|
  269. | **Figma Desktop MCP** | Read designs, extract tokens, capture screenshots from Figma | Phases 1-2, 5 |
  270. | **Figma Remote MCP** | Fallback remote Figma access | Phases 1-2, 5 |
  271. | **Chrome DevTools MCP** | Screenshots, Lighthouse audits, DOM inspection | Phases 5, 7-8 |
  272. | **Canva AI Connector** | Search, export, interact with Canva designs | Phases 1-2 (Canva) |
  273. | **Playwright MCP** | Cross-browser testing (Chromium, Firefox, WebKit) | Phases 6-7 |
  274. 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.
  275. ## Claude Code Plugin
  276. 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:
  277. ```
  278. /plugin install aurelius --marketplace PMDevSolutions/Aurelius
  279. ```
  280. 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).
  281. ## Documentation Index
  282. | Document | Location | Description |
  283. |----------|----------|-------------|
  284. | **Developer onboarding** | `docs/onboarding/README.md` | Start here -- quickstart, architecture, configuration, troubleshooting |
  285. | Quickstart guide | `docs/onboarding/quickstart.md` | Clone to running project in 10 minutes |
  286. | Architecture overview | `docs/onboarding/architecture.md` | All 56 agents, 32 skills, 4 pipelines, and how they connect |
  287. | Pipeline configuration | `docs/onboarding/pipeline-configuration.md` | Every setting in pipeline.config.json explained |
  288. | Troubleshooting FAQ | `docs/onboarding/troubleshooting.md` | Common issues and solutions |
  289. | Project instructions | `CLAUDE.md` | Full project config for Claude Code |
  290. | Figma pipeline guide | `docs/figma-to-react/README.md` | Pipeline overview and troubleshooting |
  291. | React standards | `docs/react-development/README.md` | TypeScript, Tailwind, testing conventions |
  292. | Canva pipeline guide | `docs/canva-to-react/README.md` | Canva pipeline overview and troubleshooting |
  293. | Conversation pipeline guide | `docs/conversation-to-app/README.md` | Conversational app creation via generated Figma designs |
  294. | InDesign pipeline guide | `docs/pipelines/indesign.md` | Convert exported IDML/PDF into React components, tokens, and Storybook stories |
  295. | Design system export | `docs/design-system-export/consumers.md` | Export format, round-trip re-import, and how Flavian/Nerva consume the tokens |
  296. | Desktop GUI | `docs/GUI.md` | The experimental Electron GUI: screens, commands, packaging |
  297. | Agent catalog | `.claude/CUSTOM-AGENTS-GUIDE.md` | All 56 agents with use cases |
  298. | Skills catalog | `.claude/skills/README.md` | All 32 skills with triggers |
  299. | Plugin reference | `.claude/PLUGINS-REFERENCE.md` | Aurelius as a plugin, optional plugins, expected MCP servers |
  300. | Hook system | `docs/guides/hooks.md` | The deploy guard, commit guards and reminders, and how to write a hook |
  301. | Evals | `evals/README.md` | `claude plugin eval` cases for the framework's hard rules |
  302. | Scripts reference | `scripts/README.md` | All scripts with usage examples |
  303. | Templates reference | `templates/README.md` | Starter configs and how to use them |
  304. | Pipeline config | `.claude/pipeline.config.json` | Thresholds, app types, quality gates |
  305. | Agent naming guide | `.claude/AGENT-NAMING-GUIDE.md` | Conventions for creating new agents |
  306. ## Related Projects
  307. | Project | Description |
  308. |---------|-------------|
  309. | [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) |
  310. | [AI SEO Copilot (Webflow)](https://github.com/die-Manufaktur/AI-SEO-Copilot-for-Webflow) | The original Webflow app with ~20,000 installs |
  311. | [Flavian](https://github.com/PMDevSolutions/Flavian) | Claude Code-integrated WordPress development framework with FSE block theme tools and Figma-to-WordPress pipelines |
  312. | [Nerva](https://github.com/PMDevSolutions/Nerva) | Claude Code-integrated API and backend development framework with Hono, Cloudflare Workers, and Drizzle ORM |
  313. | [Claudius](https://github.com/PMDevSolutions/Claudius) | Embeddable AI chat widget powered by Claude. React + TypeScript + Cloudflare Workers |
  314. ## Credits
  315. 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.
  316. ## License
  317. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.