akili-specs 2.1.0

package/docs/release-checklist.md

@@ -0,0 +1,91 @@
+# Release Checklist
+
+Use this checklist before publishing `akili-specs`.
+
+## Preflight
+
+- [ ] Confirm this update should be published now, not only committed to the repository.
+- [ ] Confirm all intended repo changes are committed before running the release script.
+- [ ] Confirm `CHANGELOG.md` has meaningful notes under `Unreleased`.
+- [ ] Confirm `package.json` version matches the release version.
+- [ ] Confirm `CHANGELOG.md` has a dated section for the release.
+- [ ] Confirm `releases/vX.Y.Z.md` exists.
+- [ ] Confirm npm authentication with `npm whoami --registry=https://registry.npmjs.org/`.
+- [ ] Confirm the current npm user is a maintainer for `akili-specs`.
+- [ ] Confirm package name is available or configured for the intended registry.
+- [ ] Confirm license and publishing policy.
+- [ ] Confirm no secrets, service account keys, or local config files are included.
+
+## Release Policy
+
+- Repository updates and npm updates are controlled separately.
+- Package-affecting repository changes require changelog notes before release preparation.
+- `npm run release:status` checks local release files, npm versions, remote tags, and GitHub Releases for drift.
+- The `Release Status` GitHub Actions workflow runs the same drift check on pushes, pull requests, and manual dispatches.
+- npm updates require a version bump, release notes, verification, release commit, publish, and smoke test.
+- Never publish from uncommitted changes.
+- Never claim npm is updated until publish and post-publish smoke test both succeed.
+- If publish fails, keep the release commit and fix the blocker. Do not create a replacement version unless the failed version was actually published.
+
+## Verify Locally
+
+Prepare a version bump from committed changes:
+
+```bash
+npm run release:patch
+```
+
+Use `release:minor` for new commands or workflow additions and `release:major` for breaking changes.
+
+Then verify:
+
+```bash
+npm run verify:cli
+node bin/akili.js install --tool both --dry-run
+npm run pack:dry-run
+npm run release:status
+git diff --check
+```
+
+## Verify Packed Tarball
+
+```bash
+npm pack
+npm install -g ./akili-specs-<version>.tgz
+akili install --tool both --dry-run
+akili doctor --tool claude
+```
+
+Remove the generated tarball after testing unless it is being attached to a release.
+
+## Publish
+
+For public npm publishing:
+
+```bash
+npm whoami --registry=https://registry.npmjs.org/
+npm publish --access public --registry=https://registry.npmjs.org/
+```
+
+If npm requires two-factor authentication, pass the current one-time password:
+
+```bash
+npm publish --access public --registry=https://registry.npmjs.org/ --otp=<code>
+```
+
+For private registry publishing, configure the registry first and publish using the registry's required access mode.
+
+## Post-Publish Smoke Test
+
+```bash
+pnpm dlx akili-specs@<version> list
+pnpm dlx akili-specs@<version> install --tool both --dry-run
+npm view akili-specs version --registry=https://registry.npmjs.org/
+npm run release:status
+```
+
+## GitHub Release
+
+- [ ] Tag the release, for example `v0.2.0`.
+- [ ] Create a GitHub release using `releases/v0.2.0.md`.
+- [ ] Include publish/install instructions in the release body.

package/docs/skills/README.md

@@ -0,0 +1,42 @@
+# Skill Reference
+
+AKILI ships Claude/OpenCode skills alongside the slash commands. Skills are loaded by the agent when a task needs domain-specific guidance.
+
+The installable source files live in `.claude/skills/*/SKILL.md`. These pages are the human-facing reference.
+
+## Skill Inventory
+
+| Skill | Use For | Common Commands |
+|---|---|---|
+| [`angular-developer`](angular-developer.md) | Angular architecture, components, services, signals, forms, routing, testing, CLI | `/akili-specify`, `/akili-execute`, `/akili-test`, `/akili-validate` |
+| [`api-design-principles`](api-design-principles.md) | REST and GraphQL API design and review | `/akili-constitution`, `/akili-specify`, `/akili-validate` |
+| [`aws-serverless`](aws-serverless.md) | Lambda, API Gateway, DynamoDB, SQS/SNS, SAM/CDK | `/akili-constitution`, `/akili-specify`, `/akili-execute` |
+| [`brainstorming`](brainstorming.md) | Clarifying ideas, scope, options, and trade-offs before implementation | `/akili-propose`, `/akili-specify` |
+| [`error-handling-patterns`](error-handling-patterns.md) | Exceptions, Result patterns, graceful degradation, reliability | `/akili-specify`, `/akili-execute`, `/akili-validate` |
+| [`frontend-design`](frontend-design.md) | Distinctive frontend UI and UX implementation | `/akili-constitution`, `/akili-specify`, `/akili-execute`, `/akili-test` |
+| [`gsap-core`](gsap-core.md) | Core GSAP tweens, easing, stagger, responsive and reduced-motion animation | `/akili-specify`, `/akili-execute` |
+| [`gsap-frameworks`](gsap-frameworks.md) | GSAP in Vue, Nuxt, Svelte, SvelteKit, and other non-React frameworks | `/akili-specify`, `/akili-execute` |
+| [`gsap-performance`](gsap-performance.md) | Smooth animation, transform-first motion, jank reduction | `/akili-execute`, `/akili-validate` |
+| [`gsap-plugins`](gsap-plugins.md) | GSAP plugins such as ScrollTo, Flip, Draggable, SplitText, SVG plugins | `/akili-specify`, `/akili-execute` |
+| [`gsap-react`](gsap-react.md) | GSAP in React and Next.js with cleanup and scoping | `/akili-specify`, `/akili-execute` |
+| [`gsap-scrolltrigger`](gsap-scrolltrigger.md) | Scroll-driven animation, pinning, scrub, parallax | `/akili-specify`, `/akili-execute` |
+| [`gsap-timeline`](gsap-timeline.md) | Sequenced animations and playback control | `/akili-specify`, `/akili-execute` |
+| [`gsap-utils`](gsap-utils.md) | GSAP utilities such as clamp, mapRange, random, snap, wrap | `/akili-execute` |
+| [`nestjs-expert`](nestjs-expert.md) | NestJS modules, DI, guards, interceptors, testing, TypeORM/Mongoose | `/akili-specify`, `/akili-execute`, `/akili-test`, `/akili-validate` |
+| [`product-manager-toolkit`](product-manager-toolkit.md) | Product discovery, PRDs, prioritization, customer interview analysis | `/akili-constitution`, `/akili-propose`, `/akili-specify` |
+| [`react-doctor`](react-doctor.md) | React diagnostics after changes | `/akili-test`, `/akili-validate` |
+| [`seo-audit`](seo-audit.md) | Technical, on-page, and international SEO audits with a standard finding format | `/akili-seo`, `/akili-validate` |
+| [`shadcn-ui`](shadcn-ui.md) | shadcn/ui components, forms, themes, Tailwind integration | `/akili-specify`, `/akili-execute`, `/akili-validate` |
+| [`stitch-design`](stitch-design.md) | Stitch prompt enhancement and design generation workflows | `/akili-constitution`, `/akili-specify` |
+| [`systematic-debugging`](systematic-debugging.md) | Bugs, test failures, unexpected behavior, root-cause investigation | `/akili-execute`, `/akili-test`, `/akili-validate`, `/akili-seo` |
+| [`tailwind-design-system`](tailwind-design-system.md) | Tailwind CSS v4 tokens, component systems, responsive patterns | `/akili-constitution`, `/akili-specify`, `/akili-execute` |
+| [`ui-ux-pro-max`](ui-ux-pro-max.md) | UI/UX design intelligence, palettes, typography, accessibility, stacks | `/akili-constitution`, `/akili-specify`, `/akili-execute`, `/akili-test`, `/akili-validate` |
+| [`vercel-react-best-practices`](vercel-react-best-practices.md) | React and Next.js performance and architecture guidance | `/akili-specify`, `/akili-execute`, `/akili-test`, `/akili-validate` |
+
+## Usage Rules
+
+- Use the task-specific skills listed in `tasks.md` during `/akili-execute`.
+- Use UI/UX skills when specs affect screens, flows, interactions, or accessibility.
+- Use `systematic-debugging` before proposing fixes for failures or unexpected behavior.
+- Use framework skills only when the repository or task actually uses that framework.
+- If a skill is unavailable in the host tool, fall back to the documented alternative and note the gap in the relevant report.

package/docs/skills/angular-developer.md

@@ -0,0 +1,23 @@
+# `angular-developer`
+
+## Purpose
+
+Provides Angular architecture and implementation guidance for projects, components, services, signals, forms, dependency injection, routing, SSR, accessibility, animations, styling, testing, and CLI workflows.
+
+## Use When
+
+- Creating or modifying Angular projects, components, services, directives, pipes, or routes.
+- Choosing between signal forms, template-driven forms, and reactive forms.
+- Working with Angular signals, `linkedSignal`, `resource`, or effects.
+- Reviewing Angular routing, dependency injection, accessibility, testing, or Tailwind usage.
+
+## Best Paired Commands
+
+- `/akili-specify` for Angular design and task planning.
+- `/akili-execute` for implementation.
+- `/akili-test` for Angular unit, harness, router, or E2E tests.
+- `/akili-validate` for architecture and quality checks.
+
+## Source
+
+- `../../.claude/skills/angular-developer/SKILL.md`

package/docs/skills/api-design-principles.md

@@ -0,0 +1,22 @@
+# `api-design-principles`
+
+## Purpose
+
+Guides REST and GraphQL API design so interfaces are intuitive, scalable, maintainable, and developer-friendly.
+
+## Use When
+
+- Designing a new REST or GraphQL API.
+- Reviewing endpoint shape, resource naming, status codes, pagination, filtering, or versioning.
+- Establishing API standards in project baseline docs.
+- Migrating between API paradigms.
+
+## Best Paired Commands
+
+- `/akili-constitution` for API standards in the TRD.
+- `/akili-specify` for API requirements and contracts.
+- `/akili-validate` for implementation conformance.
+
+## Source
+
+- `../../.claude/skills/api-design-principles/SKILL.md`

package/docs/skills/aws-serverless.md

@@ -0,0 +1,22 @@
+# `aws-serverless`
+
+## Purpose
+
+Guides production-ready serverless applications on AWS, including Lambda, API Gateway, DynamoDB, SQS/SNS, event-driven patterns, SAM/CDK deployment, and cold-start optimization.
+
+## Use When
+
+- Designing or reviewing AWS serverless architecture.
+- Planning Lambda APIs, queues, topics, DynamoDB tables, or event flows.
+- Documenting serverless deployment and operational constraints.
+- Optimizing cold starts or reliability in serverless systems.
+
+## Best Paired Commands
+
+- `/akili-constitution` for serverless architecture baseline.
+- `/akili-specify` for AWS-backed feature design.
+- `/akili-execute` for implementation tasks.
+
+## Source
+
+- `../../.claude/skills/aws-serverless/SKILL.md`

package/docs/skills/brainstorming.md

@@ -0,0 +1,21 @@
+# `brainstorming`
+
+## Purpose
+
+Clarifies ideas before implementation by exploring intent, scope, constraints, options, trade-offs, and approval points.
+
+## Use When
+
+- A feature or behavior change is still ambiguous.
+- A proposal needs approach options and recommendation.
+- Requirements or task sequencing need human approval before implementation.
+- UI, product, or architecture direction could branch in multiple ways.
+
+## Best Paired Commands
+
+- `/akili-propose` for intent and option exploration.
+- `/akili-specify` for requirements, design, and task planning.
+
+## Source
+
+- `../../.claude/skills/brainstorming/SKILL.md`

package/docs/skills/error-handling-patterns.md

@@ -0,0 +1,22 @@
+# `error-handling-patterns`
+
+## Purpose
+
+Guides resilient error handling across languages, including exceptions, Result types, propagation, graceful degradation, API errors, and reliability patterns.
+
+## Use When
+
+- Designing API or service error contracts.
+- Improving reliability and failure handling.
+- Defining rollback, retry, fallback, or observability behavior.
+- Auditing implementation quality around edge cases and failures.
+
+## Best Paired Commands
+
+- `/akili-specify` for error contracts in requirements and design.
+- `/akili-execute` for implementation.
+- `/akili-validate` for quality and resilience review.
+
+## Source
+
+- `../../.claude/skills/error-handling-patterns/SKILL.md`

package/docs/skills/frontend-design.md

@@ -0,0 +1,23 @@
+# `frontend-design`
+
+## Purpose
+
+Guides distinctive, production-grade frontend interfaces with intentional aesthetics, responsive behavior, accessibility, and implementation-ready structure.
+
+## Use When
+
+- Designing or implementing web UI, pages, dashboards, or components.
+- Creating a visual direction when `ui-ux-pro-max` is unavailable or too broad.
+- Reviewing UI for generic patterns, accessibility, responsiveness, or polish.
+- Translating UX intent into frontend code.
+
+## Best Paired Commands
+
+- `/akili-constitution` for the UX/UI design baseline.
+- `/akili-specify` for UI requirements and design.
+- `/akili-execute` for frontend implementation.
+- `/akili-test` and `/akili-validate` for UX checks.
+
+## Source
+
+- `../../.claude/skills/frontend-design/SKILL.md`

package/docs/skills/gsap-core.md

@@ -0,0 +1,21 @@
+# `gsap-core`
+
+## Purpose
+
+Guides GSAP core animation APIs such as `gsap.to()`, `from()`, `fromTo()`, easing, duration, stagger, defaults, `gsap.matchMedia()`, responsive animation, and reduced-motion behavior.
+
+## Use When
+
+- Adding JavaScript animation in vanilla JS or any framework.
+- Creating tweens, entrances, exits, staggered effects, or SVG/DOM motion.
+- Recommending an animation library when none is specified.
+- Handling responsive or prefers-reduced-motion animation behavior.
+
+## Best Paired Commands
+
+- `/akili-specify` for animation requirements and design.
+- `/akili-execute` for implementation.
+
+## Source
+
+- `../../.claude/skills/gsap-core/SKILL.md`

package/docs/skills/gsap-frameworks.md

@@ -0,0 +1,20 @@
+# `gsap-frameworks`
+
+## Purpose
+
+Guides GSAP usage in Vue, Nuxt, Svelte, SvelteKit, and other non-React frameworks, including lifecycle, selector scoping, and cleanup.
+
+## Use When
+
+- Animating Vue, Nuxt, Svelte, or SvelteKit components.
+- Integrating GSAP with `onMounted`, `onMount`, `onDestroy`, or framework lifecycle hooks.
+- Avoiding selector leakage or missing cleanup in framework components.
+
+## Best Paired Commands
+
+- `/akili-specify` for framework-specific animation design.
+- `/akili-execute` for implementation.
+
+## Source
+
+- `../../.claude/skills/gsap-frameworks/SKILL.md`

package/docs/skills/gsap-performance.md

@@ -0,0 +1,21 @@
+# `gsap-performance`
+
+## Purpose
+
+Optimizes GSAP animation performance by preferring transforms, avoiding layout thrashing, batching work, and reducing jank.
+
+## Use When
+
+- Animations feel choppy or miss 60fps.
+- Reviewing animation implementation for performance risk.
+- Choosing between animating transforms, opacity, layout properties, or SVG attributes.
+- Adding `will-change`, batching, or layout-safe animation patterns.
+
+## Best Paired Commands
+
+- `/akili-execute` for animation implementation.
+- `/akili-validate` for animation performance review.
+
+## Source
+
+- `../../.claude/skills/gsap-performance/SKILL.md`

package/docs/skills/gsap-plugins.md

@@ -0,0 +1,20 @@
+# `gsap-plugins`
+
+## Purpose
+
+Guides GSAP plugin usage, including registration and plugins such as ScrollToPlugin, ScrollSmoother, Flip, Draggable, Observer, SplitText, ScrambleText, SVG plugins, physics plugins, and CustomEase.
+
+## Use When
+
+- A spec needs GSAP functionality beyond core tweens.
+- Implementing Flip animations, draggable interactions, scroll-to behavior, text splitting, SVG drawing, or custom easing.
+- Reviewing plugin registration and bundle usage.
+
+## Best Paired Commands
+
+- `/akili-specify` for deciding whether plugin behavior is justified.
+- `/akili-execute` for implementation.
+
+## Source
+
+- `../../.claude/skills/gsap-plugins/SKILL.md`

package/docs/skills/gsap-react.md

@@ -0,0 +1,22 @@
+# `gsap-react`
+
+## Purpose
+
+Guides GSAP in React and Next.js, including `useGSAP`, refs, `gsap.context()`, selector scoping, and cleanup on unmount.
+
+## Use When
+
+- Animating React or Next.js components with GSAP.
+- Avoiding stale refs, duplicate animations, or missing cleanup.
+- Scoping selectors safely inside components.
+- Integrating GSAP with React lifecycle and hydration constraints.
+
+## Best Paired Commands
+
+- `/akili-specify` for React animation design.
+- `/akili-execute` for implementation.
+- `/akili-validate` for cleanup and performance review.
+
+## Source
+
+- `../../.claude/skills/gsap-react/SKILL.md`

package/docs/skills/gsap-scrolltrigger.md

@@ -0,0 +1,21 @@
+# `gsap-scrolltrigger`
+
+## Purpose
+
+Guides GSAP ScrollTrigger for scroll-linked animations, triggers, pinning, scrubbed timelines, parallax, and responsive scroll behavior.
+
+## Use When
+
+- Building scroll-driven animation, parallax, pinned sections, or progress-linked motion.
+- Reviewing ScrollTrigger setup, cleanup, refresh behavior, or responsive configuration.
+- Recommending a scroll animation approach when no library is specified.
+
+## Best Paired Commands
+
+- `/akili-specify` for scroll animation behavior and accessibility notes.
+- `/akili-execute` for implementation.
+- `/akili-validate` for motion and performance review.
+
+## Source
+
+- `../../.claude/skills/gsap-scrolltrigger/SKILL.md`

package/docs/skills/gsap-timeline.md

@@ -0,0 +1,20 @@
+# `gsap-timeline`
+
+## Purpose
+
+Guides GSAP timelines for sequencing animations, using position parameters, nesting timelines, controlling playback, and choreographing complex motion.
+
+## Use When
+
+- Multiple animation steps must be coordinated.
+- A sequence needs pause, reverse, seek, or replay control.
+- A spec needs staged entrances, page transitions, or composed motion systems.
+
+## Best Paired Commands
+
+- `/akili-specify` for animation choreography and design decisions.
+- `/akili-execute` for implementation.
+
+## Source
+
+- `../../.claude/skills/gsap-timeline/SKILL.md`

package/docs/skills/gsap-utils.md

@@ -0,0 +1,21 @@
+# `gsap-utils`
+
+## Purpose
+
+Guides `gsap.utils` helpers such as `clamp`, `mapRange`, `normalize`, `interpolate`, `random`, `snap`, `toArray`, `wrap`, and `pipe`.
+
+## Use When
+
+- Mapping scroll, pointer, or progress values into animation ranges.
+- Snapping or wrapping values.
+- Selecting DOM/SVG collections safely for animation.
+- Simplifying animation math and helper functions.
+
+## Best Paired Commands
+
+- `/akili-execute` for implementation.
+- `/akili-validate` for simplifying or reviewing animation utilities.
+
+## Source
+
+- `../../.claude/skills/gsap-utils/SKILL.md`

package/docs/skills/nestjs-expert.md

@@ -0,0 +1,23 @@
+# `nestjs-expert`
+
+## Purpose
+
+Guides NestJS architecture, modules, dependency injection, middleware, guards, interceptors, testing with Jest/Supertest, TypeORM/Mongoose integration, Passport authentication, and debugging DI issues.
+
+## Use When
+
+- Designing or modifying NestJS modules, controllers, providers, guards, interceptors, pipes, or middleware.
+- Planning API implementation inside NestJS.
+- Testing NestJS services, controllers, or integration flows.
+- Debugging dependency injection or module boundary problems.
+
+## Best Paired Commands
+
+- `/akili-specify` for backend design.
+- `/akili-execute` for implementation.
+- `/akili-test` for Jest/Supertest coverage.
+- `/akili-validate` for architecture conformance.
+
+## Source
+
+- `../../.claude/skills/nestjs-expert/SKILL.md`

package/docs/skills/product-manager-toolkit.md

@@ -0,0 +1,22 @@
+# `product-manager-toolkit`
+
+## Purpose
+
+Supports product management work, including PRDs, customer interview analysis, RICE prioritization, discovery frameworks, requirements, and go-to-market thinking.
+
+## Use When
+
+- Creating or improving `docs/prd.md`.
+- Clarifying personas, goals, scope, success metrics, or non-goals.
+- Prioritizing features or deciding whether work should proceed.
+- Turning discovery into requirements.
+
+## Best Paired Commands
+
+- `/akili-constitution` for project PRD baseline.
+- `/akili-propose` for intent and scope.
+- `/akili-specify` for behavior requirements.
+
+## Source
+
+- `../../.claude/skills/product-manager-toolkit/SKILL.md`

package/docs/skills/react-doctor.md

@@ -0,0 +1,27 @@
+# `react-doctor`
+
+## Purpose
+
+Runs React diagnostics after changes to catch security, performance, correctness, and architecture issues early.
+
+## Use When
+
+- Reviewing React code after implementation.
+- Finishing a React feature.
+- Fixing React bugs.
+- Preparing evidence for validation.
+
+## Command
+
+```bash
+npx -y react-doctor@latest . --verbose --diff
+```
+
+## Best Paired Commands
+
+- `/akili-test` for diagnostic evidence.
+- `/akili-validate` for React quality review.
+
+## Source
+
+- `../../.claude/skills/react-doctor/SKILL.md`

package/docs/skills/seo-audit.md

@@ -0,0 +1,27 @@
+# `seo-audit`
+
+## Purpose
+
+Provides an expert SEO audit framework: crawlability and indexation, technical foundations (Core Web Vitals, mobile, HTTPS), on-page optimization (titles, metas, headings, images, internal linking), international SEO (hreflang, locale canonicals, locale sitemaps), content quality (E-E-A-T), and a standard finding format.
+
+## Use When
+
+- Auditing, reviewing, or diagnosing SEO issues on a site.
+- Rankings or organic traffic dropped and the cause is unknown.
+- Reviewing meta tags, structured data, page speed, or indexing issues.
+- Running the audit phase of `/akili-seo`.
+
+## Core Rules
+
+- Findings follow the **Issue / Impact / Evidence / Fix / Priority** structure.
+- Findings are weighted by priority order: crawlability → technical → on-page → content quality → authority.
+- Static fetches (`curl`, `web_fetch`) cannot detect JS-injected JSON-LD; structured data must be validated with a rendering tool or Search Console URL inspection.
+
+## Best Paired Commands
+
+- `/akili-seo` for the audit phase (index coverage, structured data, render, on-page checks).
+- `/akili-validate` when a spec includes SEO acceptance criteria.
+
+## Source
+
+- `../../.claude/skills/seo-audit/SKILL.md`

package/docs/skills/shadcn-ui.md

@@ -0,0 +1,22 @@
+# `shadcn-ui`
+
+## Purpose
+
+Guides shadcn/ui setup and implementation, including accessible React components, React Hook Form, Zod, Tailwind themes, buttons, dialogs, dropdowns, tables, and complex forms.
+
+## Use When
+
+- Installing or configuring shadcn/ui.
+- Building accessible component patterns.
+- Implementing forms with React Hook Form and Zod.
+- Customizing Tailwind themes around shadcn/ui.
+
+## Best Paired Commands
+
+- `/akili-specify` for component and form design.
+- `/akili-execute` for implementation.
+- `/akili-validate` for accessibility and design-system review.
+
+## Source
+
+- `../../.claude/skills/shadcn-ui/SKILL.md`

package/docs/skills/stitch-design.md

@@ -0,0 +1,21 @@
+# `stitch-design`
+
+## Purpose
+
+Supports Stitch design work, including prompt enhancement, design system synthesis, and high-fidelity screen generation or editing via Stitch MCP.
+
+## Use When
+
+- Turning product intent into a high-fidelity UI prompt.
+- Creating or updating `.stitch/DESIGN.md`.
+- Generating screen designs from text.
+- Editing a Stitch-generated design.
+
+## Best Paired Commands
+
+- `/akili-constitution` for the UX/UI design baseline.
+- `/akili-specify` for UI-heavy feature design.
+
+## Source
+
+- `../../.claude/skills/stitch-design/SKILL.md`

package/docs/skills/systematic-debugging.md

@@ -0,0 +1,27 @@
+# `systematic-debugging`
+
+## Purpose
+
+Enforces root-cause debugging before proposing fixes for bugs, test failures, build failures, integration issues, performance problems, or unexpected behavior.
+
+## Use When
+
+- Any test, build, or validation check fails.
+- Production or local behavior is unexpected.
+- A previous fix did not work.
+- A multi-component issue needs data-flow tracing.
+
+## Core Rule
+
+No fixes without root-cause investigation first.
+
+## Best Paired Commands
+
+- `/akili-execute` when implementation hits failures.
+- `/akili-test` when tests fail or coverage is unclear.
+- `/akili-validate` when conformance checks fail.
+- `/akili-seo` when GSC or index data is inconsistent.
+
+## Source
+
+- `../../.claude/skills/systematic-debugging/SKILL.md`

package/docs/skills/tailwind-design-system.md

@@ -0,0 +1,23 @@
+# `tailwind-design-system`
+
+## Purpose
+
+Guides scalable design systems with Tailwind CSS v4, design tokens, component libraries, responsive patterns, and consistent utility usage.
+
+## Use When
+
+- Creating or refining a Tailwind design system.
+- Standardizing spacing, color, typography, or component tokens.
+- Building reusable component libraries.
+- Reviewing Tailwind UI implementation for consistency.
+
+## Best Paired Commands
+
+- `/akili-constitution` for the UX/UI design baseline.
+- `/akili-specify` for Tailwind component architecture.
+- `/akili-execute` for implementation.
+- `/akili-validate` for design-system compliance.
+
+## Source
+
+- `../../.claude/skills/tailwind-design-system/SKILL.md`