create-hq 5.0.0

package/template/knowledge/design-styles/ethereal-abstract.md

@@ -0,0 +1,133 @@
+# Ethereal Abstract Style Guide
+
+Visual style for social media, marketing, and brand imagery.
+
+## Mood
+Dreamy, contemplative, premium, atmospheric. Like looking through frosted glass at a beautiful sunset.
+
+## Core Principles
+1. **Abstract over literal** - Suggest rather than show
+2. **Atmosphere over detail** - Soft focus, depth, mist
+3. **Warm light over cool tech** - Golden, amber, soft blue
+4. **Organic over digital** - Natural forms, no circuits/grids
+5. **Minimal over busy** - Single focal point, negative space
+
+## Keywords for Prompts
+
+### Mood
+- Ethereal, dreamy, contemplative
+- Atmospheric, luminous, serene
+- Abstract, minimal, soft
+
+### Light
+- Golden hour, twilight, dawn
+- Soft diffused light, backlit
+- Light rays through mist/clouds
+- Bokeh, lens flare (subtle)
+
+### Texture
+- Film grain, 35mm aesthetic
+- Soft focus, shallow depth of field
+- Mist, fog, haze
+- Water reflections, ripples
+
+### Color
+- Warm amber, golden, terracotta
+- Soft teal, dusty blue, sage
+- Cream, stone, charcoal
+- Color gradients (natural, not neon)
+
+### Forms
+- Abstract light shapes
+- Cloud formations
+- Water surfaces
+- Soft geometric shapes
+- Horizon lines
+- Silhouettes (minimal)
+
+## Example Prompts
+
+### Abstract Light
+```
+Soft golden light diffusing through morning mist,
+abstract atmospheric shapes, warm amber tones,
+minimal composition, film grain, ethereal mood
+```
+
+### Color Field
+```
+Abstract color field photography, soft gradient
+from warm amber to dusty blue, minimal,
+atmospheric, out of focus light bokeh,
+contemplative mood, fine art aesthetic
+```
+
+### Natural Abstract
+```
+Close-up of light reflecting on still water,
+abstract ripple patterns, golden hour tones,
+soft focus, minimal, meditative, 35mm film
+```
+
+### Cosmic Abstract
+```
+Soft nebula-like clouds of color, ethereal
+purple and gold tones, abstract atmospheric,
+no stars or space objects, pure color and light,
+dreamy soft focus
+```
+
+### Geometric Light
+```
+Abstract soft geometric shapes formed by light,
+warm amber tones, atmospheric haze, minimal,
+like light through a prism, ethereal mood
+```
+
+## Anti-Patterns (AVOID)
+
+- Glowing orbs/particles (too AI)
+- Neon colors, cyberpunk aesthetic
+- Circuit boards, tech patterns, grids
+- Busy compositions, many elements
+- Stock photo feel, generic
+- Hard edges, sharp detail
+- Text-heavy images
+- Generic AI art aesthetic
+- Literal representations
+- People's faces (unless silhouette/abstract)
+
+## Color Palette
+
+| Use | Hex | Description |
+|-----|-----|-------------|
+| Primary Warm | #D4A574 | Golden amber |
+| Primary Cool | #7BA3A8 | Dusty teal |
+| Accent | #C17F59 | Terracotta |
+| Light | #F5EDE4 | Warm cream |
+| Dark | #2C3E50 | Deep slate |
+| Highlight | #FFD700 | Golden light |
+
+## Composition Rules
+
+1. **Single focal point** - One main element
+2. **Negative space** - At least 40% empty
+3. **Rule of thirds** - But can break for center
+4. **Horizon lines** - Often useful for grounding
+5. **Asymmetry** - More natural than centered
+6. **Depth layers** - Foreground blur, background blur
+
+## Application
+
+### Social Posts
+- Hero images: Abstract light/color fields
+- Feature announcements: Minimal + screenshot
+- Thought leadership: Atmospheric landscapes
+
+### Headers/Banners
+- Wide format color gradients
+- Abstract horizon compositions
+
+### Product
+- Dark background + clean screenshot
+- Light background for docs/guides

package/template/knowledge/design-styles/liminal-portal.md

@@ -0,0 +1,111 @@
+# Liminal Portal Style Guide
+
+Visual style for social media imagery featuring atmospheric threshold spaces.
+
+## Mood
+
+Contemplative, mysterious, transitional. Like standing at the edge of something unknown, about to step through.
+
+## Core Aesthetic
+
+- **Liminal spaces** - Thresholds, doorways, stairs, passages
+- **Architectural minimalism** - Empty spaces, clean geometry
+- **Atmospheric light** - Glowing portals, warm light sources
+- **Film grain texture** - Heavy, visible grain throughout
+- **Color gradients** - Warm center fading to cool edges
+- **High contrast** - Deep shadows against luminous highlights
+
+## Color Palette
+
+| Role | Hex | Description |
+|------|-----|-------------|
+| Light source | #F5D5C8 | Warm peach/coral glow |
+| Warm accent | #E8A87C | Soft coral |
+| Cool shadow | #3D5A5B | Muted teal |
+| Deep shadow | #1A1A1E | Near-black |
+| Transition | #5C7A7D | Teal-gray mid-tone |
+
+## Composition Rules
+
+1. **Single light source** - Usually a doorway, window, or portal
+2. **Ascending elements** - Stairs, slopes, paths leading toward light
+3. **Empty space** - No people (or distant silhouettes only)
+4. **Centered light** - Luminous area typically center or golden ratio
+5. **Surrounding darkness** - 60%+ of frame in shadow
+6. **Architectural framing** - Walls/structures create natural frame
+
+## Keywords for Prompts
+
+### Space
+- Liminal, threshold, transitional
+- Portal, doorway, passage
+- Stairs, ascending, steps
+- Empty, abandoned, quiet
+
+### Light
+- Glowing, luminous, radiant
+- Warm light source, backlit
+- Gradient light, color temperature shift
+- Dawn light, ethereal glow
+
+### Texture
+- Heavy film grain, 35mm aesthetic
+- Atmospheric haze, soft particles
+- Muted, desaturated edges
+
+### Mood
+- Contemplative, mysterious
+- Dreamlike, surreal
+- Quiet, still, suspended
+- Threshold moment, transition
+
+## Example Prompts
+
+### Classic Portal
+```
+Empty dark room with stairs leading up to a glowing
+rectangular doorway, warm light spilling through,
+heavy film grain, liminal atmosphere
+```
+
+### Architectural Threshold
+```
+Minimalist concrete interior, single illuminated
+passageway at the end, warm peach light fading to
+cool shadows, contemplative mood, grainy texture
+```
+
+### Ascending Passage
+```
+Dark stairwell ascending toward warm luminous
+opening, color gradient from coral to teal,
+empty space, film grain, mysterious atmosphere
+```
+
+## Anti-Patterns (AVOID)
+
+- Bright, well-lit scenes
+- Busy compositions, many elements
+- Neon or saturated colors
+- People prominently featured
+- Outdoor/nature scenes
+- Sharp, crisp detail (should be grainy)
+- Generic "glowing door" AI aesthetic
+- Horror/scary interpretations
+
+## When to Use
+
+- Thought leadership content (stepping into the unknown)
+- Personal growth/transformation themes
+- New chapter/beginning announcements
+- Contemplative, philosophical posts
+- Decision-point narratives
+- Career/life transition content
+
+## When NOT to Use
+
+- Upbeat, energetic content
+- Product announcements
+- Technical/how-to content
+- Team/company culture posts
+- Casual, lighthearted topics

package/template/knowledge/design-styles/swipes/american-industrial/README.md

@@ -0,0 +1,31 @@
+# American Industrial Swipes
+
+Reference images from Kyle Anthony Miller (@kyleanthony / brasshands.com)
+
+## Image Index
+
+| File | Project | Key Elements |
+|------|---------|--------------|
+| G-3m4YPW0AADdu2.jpeg | VEKTOR | Aircraft/aerospace design, cream background, technical diagrams |
+| G-JJlt5WwAABK3K.png | Takercard | Fintech cards, orange accent, modular layout |
+| G-JJmj5W0AEbJ-7.png | RC-2 | Sync platform, dark UI, status indicators |
+| G59fgNuXkAAKLJQ.jpeg | Robotic Packaging | ARC Division, industrial aesthetic, spec callouts |
+| G7fVkn3WEAAM-ST.jpeg | ARC | Robot product overview, split composition |
+| G8ECO5JWEAIksyn.png | AI-OPS | System status dashboard, dark theme, orange accent |
+| G9-3GQSWoAA8eqZ.png | Atlas | Intelligence network, orbital diagrams, infrastructure |
+| G9xEOqrXkAEZRcs.png | Design Ops Unit | Geometric overlay, corner brackets |
+| G_MVeJrXQAA8sx4.jpeg | Iris | Security layer, "Precision Built", web app |
+| G_RSkmGXkAAgAVZ.png | Forra | Platform UI, "Evolve the way you work" |
+| qyqtg7Dq.png | Brass Hands | Studio branding slide |
+
+## Usage
+
+Reference these images when applying American Industrial style:
+1. Match color palette (orange #FF5200, cream, black)
+2. Copy layout patterns (asymmetric grids, split compositions)
+3. Include signature elements (corner brackets, spec callouts, status indicators)
+4. Apply typography patterns (geometric sans headlines, monospace specs)
+
+## Source
+
+All images from x.com/kyleanthony and brasshands.com

package/template/knowledge/dev-team/README.md

@@ -0,0 +1,35 @@
+# Dev Team Knowledge Base
+
+Shared knowledge for the dev-team worker system.
+
+## Structure
+
+```
+dev-team/
+├── patterns/          # Reusable code patterns discovered during execution
+├── workflows/         # Standard worker sequences for common task types
+└── troubleshooting/   # Common issues and fixes
+```
+
+## Patterns
+
+Patterns are extracted from successful task completions:
+- Backend patterns: API design, error handling, auth flows
+- Frontend patterns: Component structure, state management
+- Database patterns: Schema design, query optimization
+- Testing patterns: E2E strategies, mocking approaches
+
+## Workflows
+
+Standard worker sequences:
+- **new-api-endpoint**: architect → database-dev → backend-dev → qa-tester
+- **new-ui-feature**: architect → frontend-dev → motion-designer → qa-tester
+- **full-stack-feature**: architect → database-dev → backend-dev → frontend-dev → qa-tester
+- **bug-fix**: qa-tester (reproduce) → backend-dev/frontend-dev → qa-tester (verify)
+
+## Troubleshooting
+
+Common issues encountered during development:
+- Build failures and resolutions
+- Test flakiness patterns
+- Integration issues between workers

package/template/knowledge/dev-team/patterns/README.md

@@ -0,0 +1,34 @@
+# Dev Patterns
+
+Reusable patterns discovered during task execution. Updated by knowledge-curator worker.
+
+## Categories
+
+- `backend/` - API design, error handling, auth flows
+- `frontend/` - Component structure, state management
+- `database/` - Schema design, query optimization
+- `testing/` - E2E strategies, mocking approaches
+- `infra/` - CI/CD, deployment, monitoring
+
+## Pattern Format
+
+Each pattern file follows:
+
+```markdown
+# Pattern Name
+
+## Problem
+What problem does this solve?
+
+## Solution
+The pattern/approach
+
+## Example
+Code example
+
+## When to Use
+Conditions for applying this pattern
+
+## Learned From
+Project/task where this was discovered
+```

package/template/knowledge/dev-team/patterns/frontend/react-best-practices.md

@@ -0,0 +1,178 @@
+# React Best Practices (Vercel)
+
+Reference: https://github.com/vercel-labs/agent-skills/tree/main/skills/react-best-practices
+
+## CRITICAL - Eliminating Waterfalls
+
+### Defer Await Until Needed
+```typescript
+// BAD - blocks everything
+async function Page() {
+  const user = await getUser();
+  const posts = await getPosts();
+  return <div>...</div>;
+}
+
+// GOOD - parallel execution
+async function Page() {
+  const userPromise = getUser();
+  const postsPromise = getPosts();
+  const [user, posts] = await Promise.all([userPromise, postsPromise]);
+  return <div>...</div>;
+}
+```
+
+### Strategic Suspense Boundaries
+```tsx
+// Wrap independent data-fetching components
+<Suspense fallback={<HeaderSkeleton />}>
+  <Header />
+</Suspense>
+<Suspense fallback={<ContentSkeleton />}>
+  <Content />
+</Suspense>
+```
+
+## CRITICAL - Bundle Optimization
+
+### Avoid Barrel File Imports
+```typescript
+// BAD - imports entire module
+import { Button } from '@/components';
+
+// GOOD - specific import
+import { Button } from '@/components/ui/Button';
+```
+
+### Dynamic Imports for Heavy Components
+```typescript
+const HeavyChart = dynamic(() => import('@/components/Chart'), {
+  loading: () => <ChartSkeleton />,
+  ssr: false
+});
+```
+
+## HIGH - Server Components
+
+### React.cache() for Deduplication
+```typescript
+import { cache } from 'react';
+
+export const getUser = cache(async (id: string) => {
+  return db.user.findUnique({ where: { id } });
+});
+```
+
+### Minimize RSC Serialization
+```tsx
+// BAD - serializes entire user object
+<ClientComponent user={user} />
+
+// GOOD - serialize only needed data
+<ClientComponent userId={user.id} userName={user.name} />
+```
+
+### Use after() for Non-Blocking Work
+```typescript
+import { after } from 'next/server';
+
+export async function POST(request: Request) {
+  const data = await saveData();
+
+  after(() => {
+    // Non-blocking: analytics, cleanup, etc.
+    sendAnalytics(data);
+  });
+
+  return Response.json(data);
+}
+```
+
+## MEDIUM - Re-render Optimization
+
+### Don't Wrap Simple Expressions
+```typescript
+// BAD - unnecessary overhead
+const doubled = useMemo(() => count * 2, [count]);
+
+// GOOD - just calculate it
+const doubled = count * 2;
+```
+
+### Functional setState Updates
+```typescript
+// BAD - stale closure risk
+setCount(count + 1);
+
+// GOOD - always current
+setCount(c => c + 1);
+```
+
+### Use Transitions for Non-Urgent Updates
+```typescript
+const [isPending, startTransition] = useTransition();
+
+function handleFilter(value: string) {
+  // Urgent: update input immediately
+  setInputValue(value);
+
+  // Non-urgent: can be interrupted
+  startTransition(() => {
+    setFilteredList(filterList(value));
+  });
+}
+```
+
+## MEDIUM - Rendering Performance
+
+### CSS content-visibility for Long Lists
+```css
+.list-item {
+  content-visibility: auto;
+  contain-intrinsic-size: 0 50px;
+}
+```
+
+### Prevent Hydration Mismatch
+```typescript
+const [mounted, setMounted] = useState(false);
+useEffect(() => setMounted(true), []);
+
+// Render placeholder on server, real content after hydration
+if (!mounted) return <Skeleton />;
+return <DynamicContent />;
+```
+
+## LOW-MEDIUM - JavaScript Performance
+
+### Set/Map for O(1) Lookups
+```typescript
+// BAD - O(n) per check
+const hasItem = items.includes(searchItem);
+
+// GOOD - O(1) lookup
+const itemSet = new Set(items);
+const hasItem = itemSet.has(searchItem);
+```
+
+### Build Index Maps
+```typescript
+// BAD - repeated O(n) lookups
+users.forEach(user => {
+  const order = orders.find(o => o.userId === user.id);
+});
+
+// GOOD - O(1) after initial build
+const ordersByUserId = new Map(orders.map(o => [o.userId, o]));
+users.forEach(user => {
+  const order = ordersByUserId.get(user.id);
+});
+```
+
+## Key Principles
+
+1. **Parallelize independent operations** - Never await sequentially
+2. **Import specifically** - Avoid barrel files
+3. **Serialize minimally** - Pass only needed data across RSC boundaries
+4. **Defer non-critical work** - Use after(), Suspense, Transitions
+5. **Measure first** - Don't optimize prematurely

package/template/knowledge/dev-team/troubleshooting/README.md

@@ -0,0 +1,31 @@
+# Troubleshooting
+
+Common issues and resolutions. Updated by knowledge-curator worker after failures.
+
+## Categories
+
+- Build failures
+- Test failures
+- Worker handoff issues
+- Context/memory issues
+
+## Issue Format
+
+```markdown
+# Issue Title
+
+## Symptoms
+What error/behavior was observed
+
+## Cause
+Root cause analysis
+
+## Resolution
+How it was fixed
+
+## Prevention
+How to avoid in future
+
+## First Seen
+Date and project/task
+```

package/template/knowledge/dev-team/workflows/README.md

@@ -0,0 +1,49 @@
+# Dev Workflows
+
+Standard worker sequences for common task types.
+
+## Available Workflows
+
+### new-api-endpoint
+For creating new API endpoints.
+```
+architect → database-dev → backend-dev → qa-tester
+```
+
+### new-ui-feature
+For pure frontend features.
+```
+architect → frontend-dev → motion-designer → qa-tester
+```
+
+### full-stack-feature
+For features touching both frontend and backend.
+```
+architect → database-dev → backend-dev → frontend-dev → qa-tester
+```
+
+### bug-fix
+For fixing reported bugs.
+```
+qa-tester (reproduce) → backend-dev/frontend-dev → qa-tester (verify)
+```
+
+### refactor
+For code refactoring.
+```
+architect (plan) → backend-dev/frontend-dev → code-reviewer → qa-tester
+```
+
+### infrastructure
+For CI/CD and deployment changes.
+```
+architect → infra-dev → qa-tester
+```
+
+## Workflow Selection
+
+Task executor analyzes issue and selects appropriate workflow based on:
+- Issue labels/tags
+- Files likely to be modified
+- PRD worker_hints field
+- Similar past issues

package/template/knowledge/hq/checkpoint-schema.json

@@ -0,0 +1,51 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "$id": "hq-checkpoint-schema",
+  "title": "HQ Checkpoint Schema",
+  "description": "Canonical checkpoint format for HQ task progress tracking",
+  "type": "object",
+  "required": ["task_id", "completed_at", "summary"],
+  "properties": {
+    "task_id": {
+      "type": "string",
+      "description": "Unique identifier for the task (e.g., US-001, feature-name)"
+    },
+    "completed_at": {
+      "type": "string",
+      "format": "date-time",
+      "description": "ISO8601 timestamp when checkpoint was created"
+    },
+    "summary": {
+      "type": "string",
+      "description": "Brief description of work completed"
+    },
+    "files_touched": {
+      "type": "array",
+      "items": { "type": "string" },
+      "description": "List of files modified during this work"
+    },
+    "build_passed": {
+      "type": "boolean",
+      "description": "Whether build/tests passed after this work"
+    },
+    "commit": {
+      "type": "string",
+      "description": "Git commit hash if code was committed"
+    },
+    "next_steps": {
+      "type": "array",
+      "items": { "type": "string" },
+      "description": "Suggested next actions for future sessions"
+    },
+    "notes": {
+      "type": "string",
+      "description": "Additional context or observations"
+    },
+    "metadata": {
+      "type": "object",
+      "description": "Arbitrary additional data",
+      "additionalProperties": true
+    }
+  },
+  "additionalProperties": false
+}