pan-stack-cli 0.1.1 → 0.1.4

package/templates/workspace/.cursor/skills/writing-guidelines/SKILL.md

@@ -0,0 +1,48 @@
+---
+name: writing-guidelines
+description: Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".
+metadata:
+  author: vercel
+  version: "1.0.0"
+  argument-hint: <file-or-pattern>
+---
+
+# Writing Guidelines
+
+Review files for compliance with Writing Guidelines.
+
+## How It Works
+
+1. Fetch the latest guidelines from the source URL below
+2. Read the specified files (or prompt user for files/pattern)
+3. Check against all rules in the fetched guidelines
+4. Output findings in the terse `file:line` format
+
+## Guidelines Source
+
+Fetch fresh guidelines before each review:
+
+```text
+https://raw.githubusercontent.com/vercel-labs/writing-guidelines/main/command.md
+```
+
+Use WebFetch to retrieve the latest rules. The fetched content contains all the rules and output format instructions.
+
+## Local Markdown Rules
+
+Also check generated or edited Markdown against local markdownlint conventions:
+
+- Keep at most one blank line between blocks. Do not create multiple consecutive blank lines. This avoids `MD012/no-multiple-blanks`.
+- Use language tags on fenced code blocks.
+- Before finishing edits, scan changed Markdown files for repeated blank lines.
+
+## Usage
+
+When a user provides a file or pattern argument:
+1. Fetch guidelines from the source URL above
+2. Read the specified files
+3. Apply all rules from the fetched guidelines
+4. Apply the local Markdown rules above
+5. Output findings using the format specified in the guidelines
+
+If no files specified, ask the user which files to review.

package/templates/workspace/.pan.yaml

@@ -0,0 +1,25 @@
+# Workspace-level commands. Per-repo commands live in apps/*/.pan.yaml
+commands:
+  install:
+    alias: i
+    description: Install dependencies across cloned repositories
+    shell: |
+      set -euo pipefail
+      root="${PAN_WORKSPACE_ROOT}"
+      for dir in apps/web apps/api; do
+        [[ -d "$root/$dir" ]] || { echo "Missing: $root/$dir (run 'pan clone' first?)" >&2; exit 1; }
+        echo "-> install $dir"
+        (cd "$root/$dir" && npm install)
+      done
+      echo "Done."
+
+  test:
+    default: web
+    description: Run tests (web | api)
+    targets:
+      web:
+        cwd: apps/web
+        exec: npm test
+      api:
+        cwd: apps/api
+        exec: npm test

package/templates/workspace/.project.yaml

@@ -0,0 +1,15 @@
+project: __PROJECT_NAME__
+managed_by: your-team
+
+stack:
+  repo: repo_url_to_be_filled
+
+repositories:
+  - name: bookshop-web
+    description: Customer-facing web application
+    url: repo_url_to_be_filled
+    path: apps/web
+  - name: bookshop-api
+    description: REST API service
+    url: repo_url_to_be_filled
+    path: apps/api

package/templates/workspace/README.md

@@ -0,0 +1,35 @@
+# __PROJECT_NAME__
+
+PAN Stack workspace shell for the Bookshop example project.
+
+This repository is the **coordination layer** — not the product source tree. It holds
+agent skills, workspace manifests, and `pan` commands. Product code lives in the
+repositories listed in `.project.yaml`.
+
+## Layout
+
+```text
+__PROJECT_NAME__/
+  .project.yaml          # Workspace manifest (repository list)
+  .pan.yaml              # Workspace-level pan commands
+  .claude/skills/        # Claude Code skills
+  .cursor/skills/        # Cursor agent skills
+  .codex/skills/         # Codex agent skills
+  apps/
+    web/                 # bookshop-web (after pan clone)
+    api/                 # bookshop-api (after pan clone)
+```
+
+## Quick start
+
+```bash
+# Edit repository URLs in .project.yaml, then:
+pan clone
+pan install
+pan test web
+```
+
+## Agent skills
+
+All three agent folders ship with the shared `writing-guidelines` skill. Add more
+skills under each `.claude`, `.cursor`, and `.codex` directory as your team grows.