@skyf0xx/hedgehog-core-full-stack-app 1.0.0

package/skills/link-workspace-packages/SKILL.md

@@ -0,0 +1,41 @@
+---
+name: link-workspace-packages
+description: 'Link workspace packages in the Hedgehog pnpm monorepo. USE WHEN: (1) you just created or generated new packages and need to wire up their dependencies, (2) code imports from a sibling package and needs it added as a dependency, (3) you get resolution errors for workspace packages (@org/*) like "cannot find module", "failed to resolve import", "TS2307", or "cannot resolve". DO NOT patch around with tsconfig paths or manual package.json edits - use pnpm''s workspace commands to fix actual linking.'
+---
+
+# Link Workspace Packages
+
+Add dependencies between packages in the workspace using pnpm's `workspace:` protocol — symlinks are only created when a dependency is explicitly declared this way.
+
+## Workflow
+
+1. Identify consumer package (the one importing)
+2. Identify provider package(s) (being imported)
+3. Add the dependency:
+
+   ```bash
+   # From consumer directory
+   pnpm add @org/ui --workspace
+
+   # Or with --filter from anywhere
+   pnpm add @org/ui --filter @org/app --workspace
+   ```
+
+   Result in `package.json`:
+
+   ```json
+   { "dependencies": { "@org/ui": "workspace:*" } }
+   ```
+
+4. Verify the symlink was created in the consumer's `node_modules/@org/<package>`
+
+## Debugging "Cannot find module"
+
+1. Check if the dependency is declared in the consumer's `package.json`
+2. If not, add it using the command above
+3. Run `pnpm install`
+
+## Notes
+
+- pnpm uses strict isolation (no hoisting) — a package must be an explicit dependency to be resolvable, even if it's installed elsewhere in the workspace. This prevents phantom deps.
+- Root `package.json` should have `"private": true` to prevent accidental publish.

package/skills/nx-generate/SKILL.md

@@ -0,0 +1,165 @@
+---
+name: nx-generate
+description: Generate code using nx generators. INVOKE IMMEDIATELY when user mentions scaffolding, setup, structure, creating apps/libs, or setting up project structure. Trigger words - scaffold, setup, create a new app, create a new lib, project structure, generate, add a new project. ALWAYS use this BEFORE calling nx_docs or exploring - this skill handles discovery internally.
+subagent: general-purpose
+context: fork
+---
+
+# Run Nx Generator
+
+Nx generators are powerful tools that scaffold projects, make automated code migrations or automate repetitive tasks in a monorepo. They ensure consistency across the codebase and reduce boilerplate work.
+
+This skill applies when the user wants to:
+
+- Create new projects like libraries or applications
+- Scaffold features or boilerplate code
+- Run workspace-specific or custom generators
+- Do anything else that an nx generator exists for
+
+## Key Principles
+
+1. **Always use `--no-interactive`** - Prevents prompts that would hang execution
+2. **Read the generator source code** - The schema alone is not enough; understand what the generator actually does
+3. **Match existing repo patterns** - Study similar artifacts in the repo and follow their conventions
+4. **Verify with lint/test/build/typecheck etc.** - Generated code must pass verification, using whatever targets are appropriate for this workspace (CI config is a good guide for which ones are critical).
+
+## Steps
+
+### 1. Discover Available Generators
+
+Use the Nx CLI to discover available generators:
+
+- List all generators for a plugin: `pnpm nx list @nx/react`
+- View available plugins: `pnpm nx list`
+
+This includes plugin generators (e.g., `@nx/react:library`) and local workspace generators.
+
+### 2. Match Generator to User Request
+
+Identify which generator(s) could fulfill the user's needs. Consider what artifact type they want, which framework is relevant, and any specific generator names mentioned.
+
+**IMPORTANT**: When both a local workspace generator and an external plugin generator could satisfy the request, **always prefer the local workspace generator**. Local generators are customized for the specific repo's patterns.
+
+If no suitable generator exists, you can stop using this skill. However, the burden of proof is high—carefully consider all available generators before deciding none apply.
+
+### 3. Get Generator Options
+
+Use the `--help` flag to understand available options:
+
+```bash
+pnpm nx g @nx/react:library --help
+```
+
+Pay attention to required options, defaults that might need overriding, and options relevant to the user's request.
+
+### Library Buildability
+
+**Default to non-buildable libraries** unless there's a specific reason for buildable.
+
+| Type                        | When to use                                                       | Generator flags                     |
+| --------------------------- | ----------------------------------------------------------------- | ----------------------------------- |
+| **Non-buildable** (default) | Internal monorepo libs consumed by apps                           | No `--bundler` flag                 |
+| **Buildable**               | Publishing to npm, cross-repo sharing, stable libs for cache hits | `--bundler=vite` or `--bundler=swc` |
+
+Non-buildable libs:
+
+- Export `.ts`/`.tsx` source directly
+- Consumer's bundler compiles them
+- Faster dev experience, less config
+
+Buildable libs:
+
+- Have their own build target
+- Useful for stable libs that rarely change (cache hits)
+- Required for npm publishing
+
+**If unclear, ask the user:** "Should this library be buildable (own build step, better caching) or non-buildable (source consumed directly, simpler setup)?"
+
+### 4. Read Generator Source Code
+
+**This step is critical.** The schema alone does not tell you everything. Reading the source code helps you:
+
+- Know exactly what files will be created/modified and where
+- Understand side effects (updating configs, installing deps, etc.)
+- Identify behaviors and options not obvious from the schema
+- Understand how options interact with each other
+
+To find generator source code:
+
+- For plugin generators: Use `node -e "console.log(require.resolve('@nx/<plugin>/generators.json'));"` to find the generators.json, then locate the source from there
+- If that fails, read directly from `node_modules/<plugin>/generators.json`
+- For local generators: Typically in `tools/generators/` or a local plugin directory. Search the repo for the generator name.
+
+After reading the source, reconsider: Is this the right generator? If not, go back to step 2.
+
+> **⚠️ `--directory` flag behavior can be misleading.**
+> It should specify the full path of the generated library or component, not the parent path that it will be generated in.
+>
+> ```bash
+> # ✅ Correct - directory is the full path for the library
+> nx g @nx/react:library --directory=libs/my-lib
+> # generates libs/my-lib/package.json and more
+>
+> # ❌ Wrong - this will create files at libs and libs/src/...
+> nx g @nx/react:library --name=my-lib --directory=libs
+> # generates libs/package.json and more
+> ```
+
+### 5. Examine Existing Patterns
+
+Before generating, examine the target area of the codebase:
+
+- Look at similar existing artifacts (other libraries, applications, etc.)
+- Identify naming conventions, file structures, and configuration patterns
+- Note which test runners, build tools, and linters are used
+- Configure the generator to match these patterns
+
+### 6. Dry-Run to Verify File Placement
+
+**Always run with `--dry-run` first** to verify files will be created in the correct location:
+
+```bash
+pnpm nx g @nx/react:library --name=my-lib --dry-run --no-interactive
+```
+
+Review the output carefully. If files would be created in the wrong location, adjust your options based on what you learned from the generator source code.
+
+Note: Some generators don't support dry-run (e.g., if they install npm packages). If dry-run fails for this reason, proceed to running the generator for real.
+
+### 7. Run the Generator
+
+Execute the generator:
+
+```bash
+pnpm nx generate <generator-name> <options> --no-interactive
+```
+
+> **Tip:** New packages often need workspace dependencies wired up (e.g., importing shared types, being consumed by apps). The `link-workspace-packages` skill can help add these correctly.
+
+### 8. Modify Generated Code (If Needed)
+
+Generators provide a starting point. Modify the output as needed to:
+
+- Add or modify functionality as requested
+- Adjust imports, exports, or configurations
+- Integrate with existing code patterns
+
+**Important:** If you replace or delete generated test files (e.g., `*.spec.ts`), either write meaningful replacement tests or remove the `test` target from the project configuration. Empty test suites will cause `nx test` to fail.
+
+### 9. Format and Verify
+
+Format all generated/modified files:
+
+```bash
+pnpm nx format --fix
+```
+
+This example is for built-in nx formatting with prettier. There might be other formatting tools for this workspace, use these when appropriate.
+
+Then verify the generated code works. Keep in mind that the changes you make with a generator or subsequent modifications might impact various projects so it's usually not enough to only run targets for the artifact you just created.
+
+```bash
+pnpm nx run-many -t build,lint,test,typecheck
+```
+
+If verification fails with manageable issues (a few lint errors, minor type issues), fix them. If issues are extensive, attempt obvious fixes first, then escalate to the user with details about what was generated, what's failing, and what you've attempted.

package/skills/nx-run-tasks/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: nx-run-tasks
+description: Helps with running tasks in an Nx workspace. USE WHEN the user wants to execute build, test, lint, serve, or run any other tasks defined in the workspace.
+---
+
+Run tasks via `pnpm nx` (see the `nx-workspace` skill for the pnpm-only convention and for checking which targets a project has before running one).
+
+For more details on any command, run it with `--help` (e.g. `pnpm nx run-many --help`, `pnpm nx affected --help`).
+
+## Run a single task
+
+```
+pnpm nx run <project>:<task>
+```
+
+where `project` is the project name defined in `package.json` or `project.json` (if present).
+
+## Run multiple tasks
+
+```
+pnpm nx run-many -t build test lint typecheck
+```
+
+You can pass a `-p` flag to filter to specific projects, otherwise it runs on all projects. You can also use `--exclude` to exclude projects, and `--parallel` to control the number of parallel processes (default is 3).
+
+Examples:
+
+- `pnpm nx run-many -t test -p proj1 proj2` — test specific projects
+- `pnpm nx run-many -t test --projects=*-app --exclude=excluded-app` — test projects matching a pattern
+- `pnpm nx run-many -t test --projects=tag:api-*` — test projects by tag
+
+## Run tasks for affected projects
+
+Use `pnpm nx affected` to only run tasks on projects that have been changed and projects that depend on changed projects. This is especially useful in CI and for large workspaces.
+
+```
+pnpm nx affected -t build test lint
+```
+
+By default it compares against the base branch. You can customize this:
+
+- `pnpm nx affected -t test --base=main --head=HEAD` — compare against a specific base and head
+- `pnpm nx affected -t test --files=libs/mylib/src/index.ts` — specify changed files directly
+
+## Useful flags
+
+These flags work with `run`, `run-many`, and `affected`:
+
+- `--skipNxCache` — rerun tasks even when results are cached
+- `--verbose` — print additional information such as stack traces
+- `--nxBail` — stop execution after the first failed task
+- `--configuration=<name>` — use a specific configuration (e.g. `production`)

package/skills/nx-workspace/SKILL.md

@@ -0,0 +1,261 @@
+---
+name: nx-workspace
+description: "Explore and understand Nx workspaces. USE WHEN answering questions about the workspace, projects, or tasks. ALSO USE WHEN an nx command fails or you need to check available targets/configuration before running a task. EXAMPLES: 'What projects are in this workspace?', 'How is project X configured?', 'What depends on library Y?', 'What targets can I run?', 'Cannot find configuration for task', 'debug nx task failure'."
+---
+
+# Nx Workspace Exploration
+
+This skill provides read-only exploration of Nx workspaces. Use it to understand workspace structure, project configuration, available targets, and dependencies.
+
+Run all commands via `pnpm nx` (Hedgehog workspaces are pnpm-only).
+
+## Listing Projects
+
+Use `pnpm nx show projects` to list projects in the workspace.
+
+The project filtering syntax (`-p`/`--projects`) works across many Nx commands including `nx run-many`, `nx release`, `nx show projects`, and more. Filters support explicit names, glob patterns, tag references (e.g. `tag:name`), directories, and negation (e.g. `!project-name`).
+
+```bash
+# List all projects
+pnpm nx show projects
+
+# Filter by pattern (glob)
+pnpm nx show projects --projects "apps/*"
+pnpm nx show projects --projects "shared-*"
+
+# Filter by tag
+pnpm nx show projects --projects "tag:publishable"
+pnpm nx show projects -p 'tag:publishable,!tag:internal'
+
+# Filter by target (projects that have a specific target)
+pnpm nx show projects --withTarget build
+
+# Combine filters
+pnpm nx show projects --type lib --withTarget test
+pnpm nx show projects --affected --exclude="*-e2e"
+pnpm nx show projects -p "tag:scope:client,packages/*"
+
+# Negate patterns
+pnpm nx show projects -p '!tag:private'
+pnpm nx show projects -p '!*-e2e'
+
+# Output as JSON
+pnpm nx show projects --json
+```
+
+## Project Configuration
+
+Use `pnpm nx show project <name> --json` to get the full resolved configuration for a project.
+
+**Important**: Do NOT read `project.json` directly - it only contains partial configuration. The `nx show project --json` command returns the full resolved config including inferred targets from plugins.
+
+You can read the full project schema at `node_modules/nx/schemas/project-schema.json` to understand nx project configuration options.
+
+```bash
+# Get full project configuration
+pnpm nx show project my-app --json
+
+# Extract specific parts from the JSON
+pnpm nx show project my-app --json | jq '.targets'
+pnpm nx show project my-app --json | jq '.targets.build'
+pnpm nx show project my-app --json | jq '.targets | keys'
+
+# Check project metadata
+pnpm nx show project my-app --json | jq '{name, root, sourceRoot, projectType, tags}'
+```
+
+## Target Information
+
+Targets define what tasks can be run on a project.
+
+```bash
+# List all targets for a project
+pnpm nx show project my-app --json | jq '.targets | keys'
+
+# Get full target configuration
+pnpm nx show project my-app --json | jq '.targets.build'
+
+# Check target executor/command
+pnpm nx show project my-app --json | jq '.targets.build.executor'
+pnpm nx show project my-app --json | jq '.targets.build.command'
+
+# View target options
+pnpm nx show project my-app --json | jq '.targets.build.options'
+
+# Check target inputs/outputs (for caching)
+pnpm nx show project my-app --json | jq '.targets.build.inputs'
+pnpm nx show project my-app --json | jq '.targets.build.outputs'
+
+# Find projects with a specific target
+pnpm nx show projects --withTarget serve
+pnpm nx show projects --withTarget e2e
+```
+
+## Workspace Configuration
+
+Read `nx.json` directly for workspace-level configuration.
+You can read the full project schema at `node_modules/nx/schemas/nx-schema.json` to understand nx project configuration options.
+
+```bash
+# Read the full nx.json
+cat nx.json
+
+# Or use jq for specific sections
+cat nx.json | jq '.targetDefaults'
+cat nx.json | jq '.namedInputs'
+cat nx.json | jq '.plugins'
+cat nx.json | jq '.generators'
+```
+
+Key nx.json sections:
+
+- `targetDefaults` - Default configuration applied to all targets of a given name
+- `namedInputs` - Reusable input definitions for caching
+- `plugins` - Nx plugins and their configuration
+
+## Affected Projects
+
+If the user is asking about affected projects, read the [affected projects reference](references/AFFECTED.md) for detailed commands and examples.
+
+## Programmatic Answers
+
+When processing nx CLI results, use command-line tools to compute the answer programmatically rather than counting or parsing output manually. Always use `--json` flags to get structured output that can be processed with `jq`, `grep`, or other tools you have installed locally.
+
+### Listing Projects ("What's in this workspace?")
+
+```bash
+pnpm nx show projects --json
+```
+
+Example output:
+
+```json
+["my-app", "my-app-e2e", "shared-ui", "shared-utils", "api"]
+```
+
+Common operations:
+
+```bash
+# Count projects
+pnpm nx show projects --json | jq 'length'
+
+# Filter by pattern
+pnpm nx show projects --json | jq '.[] | select(startswith("shared-"))'
+
+# Get affected projects as array
+pnpm nx show projects --affected --json | jq '.'
+```
+
+### Project Details ("How do I build/test/lint project X?")
+
+```bash
+pnpm nx show project my-app --json
+```
+
+Example output:
+
+```json
+{
+  "root": "apps/my-app",
+  "name": "my-app",
+  "sourceRoot": "apps/my-app/src",
+  "projectType": "application",
+  "tags": ["type:app", "scope:client"],
+  "targets": {
+    "build": {
+      "executor": "@nx/vite:build",
+      "options": { "outputPath": "dist/apps/my-app" }
+    },
+    "serve": {
+      "executor": "@nx/vite:dev-server",
+      "options": { "buildTarget": "my-app:build" }
+    },
+    "test": {
+      "executor": "@nx/vite:test",
+      "options": {}
+    }
+  },
+  "implicitDependencies": []
+}
+```
+
+Common operations:
+
+```bash
+# Get target names
+pnpm nx show project my-app --json | jq '.targets | keys'
+
+# Get specific target config
+pnpm nx show project my-app --json | jq '.targets.build'
+
+# Get tags
+pnpm nx show project my-app --json | jq '.tags'
+
+# Get project root
+pnpm nx show project my-app --json | jq -r '.root'
+```
+
+### Project Graph ("What depends on library Y?")
+
+```bash
+pnpm nx graph --print
+```
+
+Example output:
+
+```json
+{
+  "graph": {
+    "nodes": {
+      "my-app": {
+        "name": "my-app",
+        "type": "app",
+        "data": { "root": "apps/my-app", "tags": ["type:app"] }
+      },
+      "shared-ui": {
+        "name": "shared-ui",
+        "type": "lib",
+        "data": { "root": "libs/shared-ui", "tags": ["type:ui"] }
+      }
+    },
+    "dependencies": {
+      "my-app": [
+        { "source": "my-app", "target": "shared-ui", "type": "static" }
+      ],
+      "shared-ui": []
+    }
+  }
+}
+```
+
+Common operations:
+
+```bash
+# Get all project names from graph
+pnpm nx graph --print | jq '.graph.nodes | keys'
+
+# Find dependencies of a project
+pnpm nx graph --print | jq '.graph.dependencies["my-app"]'
+
+# Find projects that depend on a library
+pnpm nx graph --print | jq '.graph.dependencies | to_entries[] | select(.value[].target == "shared-ui") | .key'
+```
+
+## Troubleshooting
+
+### "Cannot find configuration for task X:target"
+
+```bash
+# Check what targets exist on the project
+pnpm nx show project X --json | jq '.targets | keys'
+
+# Check if any projects have that target
+pnpm nx show projects --withTarget target
+```
+
+### "The workspace is out of sync"
+
+```bash
+pnpm nx sync
+pnpm nx reset  # if sync doesn't fix stale cache
+```

package/skills/nx-workspace/references/AFFECTED.md

@@ -0,0 +1,27 @@
+## Affected Projects
+
+Find projects affected by changes in the current branch.
+
+```bash
+# Affected since base branch (auto-detected)
+pnpm nx show projects --affected
+
+# Affected with explicit base
+pnpm nx show projects --affected --base=main
+pnpm nx show projects --affected --base=origin/main
+
+# Affected between two commits
+pnpm nx show projects --affected --base=abc123 --head=def456
+
+# Affected apps only
+pnpm nx show projects --affected --type app
+
+# Affected excluding e2e projects
+pnpm nx show projects --affected --exclude="*-e2e"
+
+# Affected by uncommitted changes
+pnpm nx show projects --affected --uncommitted
+
+# Affected by untracked files
+pnpm nx show projects --affected --untracked
+```

package/vendor-skills/GSAP/ATTRIBUTION.md

@@ -0,0 +1,30 @@
+# Attribution
+
+This directory vendors the skill shelf from
+[gsap-skills](https://github.com/greensock/gsap-skills) (`greensock/gsap-skills`),
+MIT-licensed. See `LICENSE` in this directory for the full license text.
+
+- **Source repo:** https://github.com/greensock/gsap-skills
+- **Vendored from:** `main` branch, commit `aed9cfd3277740755f6bfc1155c7aa645403b760`
+- **Vendored on:** 2026-07-27
+
+## What's vendored
+
+All eight skills from the source repo's `skills/` directory, plus the
+skill index, unmodified:
+
+- `gsap-core`, `gsap-timeline`, `gsap-scrolltrigger`, `gsap-plugins`,
+  `gsap-utils`, `gsap-react`, `gsap-performance`, `gsap-frameworks`
+- `llms.txt` (skill index: names, summaries, trigger terms)
+
+The source repo's plugin scaffolding (`.claude-plugin/`, `.cursor-plugin/`),
+Copilot instructions (`.github/`), assets, and framework example apps
+(`examples/`) are not vendored — Hedgehog's own agents (`front-end-eng`,
+`ux-planner`) are the entry point into these skills, not a marketplace
+install or per-agent instruction file.
+
+## Re-vendoring
+
+Pinned deliberately. Re-vendoring against a newer gsap-skills commit is a
+manual act: repeat the fetch against the new ref and update this file's
+pinned commit and date.

package/vendor-skills/GSAP/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 GreenSock
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.