paw-ps-setup skill by pawbytes

Prodig Suites Setup

Overview

Installs and configures Prodig Suites into a project. Prodig Suites is a product creation system that guides users from vague idea to production-ready product, supporting four product families: Knowledge, Template, Software, and Service.

This setup skill scaffolds the complete workspace structure including:

{project-root}/.pawbytes/prodig-suites/ — Module root
{project-root}/.pawbytes/prodig-suites/memory/paw-ps-sidecar/ — Shared memory sidecar
{project-root}/.pawbytes/prodig-suites/products/ — Product workspaces
{project-root}/.pawbytes/prodig-suites/artifacts/ — Generated outputs

Configuration is written to the Pawbytes ecosystem config:

{project-root}/.pawbytes/config/config.yaml — Shared project config with ps: section for module-specific values
{project-root}/.pawbytes/config/config.user.yaml — Personal settings (user_name, communication_language)
{project-root}/.pawbytes/config/module-help.csv — Registers module capabilities

{project-root} is a literal token in config values — never substitute it with an actual path. It signals to the consuming LLM that the value is relative to the project root.

Principles

Sensible defaults: Every setting has a reasonable default; users only override what matters to them
Idempotent setup: Running setup multiple times preserves existing work and memory
Clear confirmation: Show exactly what will change before writing files
Progressive disclosure: Scaffold starter files with headings and brief instructions, not full content
Capability detection: Verify optional research/reporting capabilities and note what's missing

On Activation

Read ./assets/module.yaml for module metadata and variable definitions (the code field ps is the module identifier)
Check if {project-root}/.pawbytes/prodig-suites/ exists — if present, inform the user this is an update
Check for core Pawbytes config at {project-root}/.pawbytes/config/config.yaml

If the user provides arguments (e.g. accept all defaults, --headless, or inline values like default mode is template, quality bar is publish-ready), map any provided values to config keys, use defaults for the rest, and skip interactive prompting. Still display the full confirmation summary at the end.

Collect Configuration

Ask the user for values. Show defaults in brackets. Present all values together so the user can respond once with only the values they want to change (e.g. "change quality bar to publish-ready, rest are fine"). Never tell the user to "press enter" or "leave blank" — in a chat interface they must type something to respond.

Default priority (highest wins): existing config values > ./assets/module.yaml defaults.

Core config (only if no core keys exist yet): user_name (default: Pawbytes), communication_language and document_output_language (default: English — ask as a single language question, both keys get the same answer). Of these, user_name and communication_language are written exclusively to config.user.yaml.

Module config: Read each variable in ./assets/module.yaml that has a prompt field. Ask using that prompt with its default value.

Load ./references/config-variables.md for detailed descriptions of each configuration variable.

Create Directory Structure

After collecting configuration, create the complete workspace structure:

Note: {project-root} is a literal token that resolves to the project root directory at runtime. Do not substitute it with an actual path.

# Main module directories
mkdir -p "{project-root}/.pawbytes/prodig-suites/memory/paw-ps-sidecar/curated/product-types"
mkdir -p "{project-root}/.pawbytes/prodig-suites/memory/paw-ps-sidecar/daily"
mkdir -p "{project-root}/.pawbytes/prodig-suites/products"
mkdir

Create Sidecar Files

1. Create index.md (Orientation File)

Create {project-root}/.pawbytes/prodig-suites/memory/paw-ps-sidecar/index.md:

2. Create Starter Curated Files

Create each curated file with headings and brief instructions:

product-context.md

market-intelligence.md

audience-intelligence.md

product-decisions.md

output-standards.md

3. Create Product Type Files

Create {project-root}/.pawbytes/prodig-suites/memory/paw-ps-sidecar/curated/product-types/:

knowledge-products.md

# Knowledge Products
 
Best practices and structures for courses, ebooks, guides, and memberships.
 
## Product Types
 
### Courses
- Define learning outcomes first
- Structure in modules → lessons → topics
- Include practice activities
- Plan assessments
 
### Ebooks/Guides
- Define reader transformation
- Structure in chapters → sections
- Include examples and templates
- Plan call-to-actions
 
### Memberships
- Define content pillars
- Plan release cadence
- Structure access levels
- Design community elements
 
## Output Structure
 
```text
knowledge-product/
├── curriculum.md        # Course outline or chapter structure
├── modules/
│   ├── module-1.md
│   └── ...
├── materials/           # Supporting materials
└── assets/              # Images, downloads, etc.
```
 
## Quality Checklist
 
- [ ] Learning objectives defined
- [ ] Logical progression verified
- [ ] Practice activities included
- [ ] All content complete (no placeholders)

template-products.md

# Template Products
 
Best practices for templates, prompt packs, and digital kits.
 
## Product Types
 
### Templates
- Solve specific problems
- Include clear instructions
- Use placeholder conventions
- Design for reusability
 
### Prompt Packs
- Group by use case
- Include example outputs
- Document parameters
- Provide variation templates
 
### Digital Kits
- Combine complementary assets
- Provide assembly guide
- Include source files
- Document dependencies
 
## Output Structure
 
```text
template-product/
├── templates/
│   └── template-1.{ext}
├── guide.md            # Usage instructions
├── examples/           # Example outputs
└── assets/             # Supporting files
```
 
## Quality Checklist
 
- [ ] Templates are functional
- [ ] Instructions are clear
- [ ] Formatting is consistent
- [ ] Design is reusable

software-products.md

# Software Products
 
Best practices for SaaS, apps, and AI tools.
 
## Product Types
 
### SaaS/Apps
- Define core value proposition
- Map user journeys
- Define MVP features
- Plan technical architecture
 
### AI Tools
- Define AI capabilities
- Document prompts/flows
- Plan integrations
- Design user interface
 
## Output Structure
 
```text
software-product/
├── prd-lite.md         # Product requirements
├── features/
│   └── feature-1.md
├── user-flows/
│   └── flow-1.md
└── technical/
    └── architecture.md
```
 
## Quality Checklist
 
- [ ] Value proposition clear
- [ ] MVP scope defined
- [ ] User flows documented
- [ ] Technical requirements stated

service-products.md

# Service Products
 
Best practices for productized services and consulting packages.
 
## Product Types
 
### Productized Services
- Define clear deliverables
- Set scope boundaries
- Standardize process
- Create pricing tiers
 
### Consulting Packages
- Define outcomes
- Structure engagements
- Create templates
- Document process
 
## Output Structure
 
```text
service-product/
├── offer.md            # Offer structure and pricing
├── deliverables/
│   └── deliverable-1.md
├── process.md          # Delivery process
└── templates/          # Service delivery templates
```
 
## Quality Checklist
 
- [ ] Deliverables are clear
- [ ] Scope is bounded
- [ ] Pricing is defined
- [ ] Process is documented

Verify Capabilities

Check for optional capabilities that enhance Prodig Suites:

Research Capabilities

Web search tool available (WebSearch, mcp__exa__web_search_exa)
Code graph context available (mcp__CodeGraphContext__*)

Reporting Capabilities

Presentation generation available (paw-tools-presentation)
Release tools available (paw-tools-release)

Note any missing capabilities in the confirmation message. These are optional but enhance the suite's power.

Write Files

Write a temp JSON file with the collected answers structured as {"core": {...}, "module": {...}} (omit core if it already exists). Then run both scripts:

Both scripts output JSON to stdout with results. If either exits non-zero, surface the error and stop.

Run ./scripts/merge-config.py --help or ./scripts/merge-help-csv.py --help for full usage.

Confirm

Use the script JSON output to display what was written — config values set, user settings written to config.user.yaml (user_keys in result), help entries added, fresh install vs update. Then display the module_greeting from ./assets/module.yaml to the user.

Display a comprehensive summary:

Then display the module_greeting from ./assets/module.yaml.

Outcome

Once the user's user_name and communication_language are known (from collected input, arguments, or existing config), use them consistently for the remainder of the session: address the user by their configured name and communicate in their configured language.

Output Contract

Once setup completes, the following are guaranteed:

Action type: Module installation/configuration
Files created:
- {project-root}/.pawbytes/prodig-suites/ directory structure
- {project-root}/.pawbytes/prodig-suites/memory/paw-ps-sidecar/index.md
- {project-root}/.pawbytes/prodig-suites/memory/paw-ps-sidecar/curated/*.md
- {project-root}/.pawbytes/prodig-suites/memory/paw-ps-sidecar/curated/product-types/*.md
- {project-root}/.pawbytes/config/config.user.yaml (if core config collected)
Recommendations: Suggest running paw-ps-agent-product-builder to start first product
File saved to: {project-root}/.pawbytes/prodig-suites/*

Prodig Suites Setup

Overview

This setup skill scaffolds the complete workspace structure including:

{project-root}/.pawbytes/prodig-suites/ — Module root
{project-root}/.pawbytes/prodig-suites/memory/paw-ps-sidecar/ — Shared memory sidecar
{project-root}/.pawbytes/prodig-suites/products/ — Product workspaces
{project-root}/.pawbytes/prodig-suites/artifacts/ — Generated outputs

Configuration is written to the Pawbytes ecosystem config:

{project-root}/.pawbytes/config/config.yaml — Shared project config with ps: section for module-specific values
{project-root}/.pawbytes/config/config.user.yaml — Personal settings (user_name, communication_language)
{project-root}/.pawbytes/config/module-help.csv — Registers module capabilities

{project-root} is a literal token in config values — never substitute it with an actual path. It signals to the consuming LLM that the value is relative to the project root.

Principles

Sensible defaults: Every setting has a reasonable default; users only override what matters to them
Idempotent setup: Running setup multiple times preserves existing work and memory
Clear confirmation: Show exactly what will change before writing files
Progressive disclosure: Scaffold starter files with headings and brief instructions, not full content
Capability detection: Verify optional research/reporting capabilities and note what's missing

On Activation

Read ./assets/module.yaml for module metadata and variable definitions (the code field ps is the module identifier)
Check if {project-root}/.pawbytes/prodig-suites/ exists — if present, inform the user this is an update
Check for core Pawbytes config at {project-root}/.pawbytes/config/config.yaml

Collect Configuration

Default priority (highest wins): existing config values > ./assets/module.yaml defaults.

Module config: Read each variable in ./assets/module.yaml that has a prompt field. Ask using that prompt with its default value.

Load ./references/config-variables.md for detailed descriptions of each configuration variable.

Create Directory Structure

After collecting configuration, create the complete workspace structure:

Note: {project-root} is a literal token that resolves to the project root directory at runtime. Do not substitute it with an actual path.

# Main module directories
mkdir -p "{project-root}/.pawbytes/prodig-suites/memory/paw-ps-sidecar/curated/product-types"
mkdir -p "{project-root}/.pawbytes/prodig-suites/memory/paw-ps-sidecar/daily"
mkdir -p "{project-root}/.pawbytes/prodig-suites/products"
mkdir

Create Sidecar Files

1. Create index.md (Orientation File)

Create {project-root}/.pawbytes/prodig-suites/memory/paw-ps-sidecar/index.md:

2. Create Starter Curated Files

Create each curated file with headings and brief instructions:

product-context.md

market-intelligence.md

audience-intelligence.md

product-decisions.md

output-standards.md

3. Create Product Type Files

Create {project-root}/.pawbytes/prodig-suites/memory/paw-ps-sidecar/curated/product-types/:

knowledge-products.md

# Knowledge Products
 
Best practices and structures for courses, ebooks, guides, and memberships.
 
## Product Types
 
### Courses
- Define learning outcomes first
- Structure in modules → lessons → topics
- Include practice activities
- Plan assessments
 
### Ebooks/Guides
- Define reader transformation
- Structure in chapters → sections
- Include examples and templates
- Plan call-to-actions
 
### Memberships
- Define content pillars
- Plan release cadence
- Structure access levels
- Design community elements
 
## Output Structure
 
```text
knowledge-product/
├── curriculum.md        # Course outline or chapter structure
├── modules/
│   ├── module-1.md
│   └── ...
├── materials/           # Supporting materials
└── assets/              # Images, downloads, etc.
```
 
## Quality Checklist
 
- [ ] Learning objectives defined
- [ ] Logical progression verified
- [ ] Practice activities included
- [ ] All content complete (no placeholders)

template-products.md

# Template Products
 
Best practices for templates, prompt packs, and digital kits.
 
## Product Types
 
### Templates
- Solve specific problems
- Include clear instructions
- Use placeholder conventions
- Design for reusability
 
### Prompt Packs
- Group by use case
- Include example outputs
- Document parameters
- Provide variation templates
 
### Digital Kits
- Combine complementary assets
- Provide assembly guide
- Include source files
- Document dependencies
 
## Output Structure
 
```text
template-product/
├── templates/
│   └── template-1.{ext}
├── guide.md            # Usage instructions
├── examples/           # Example outputs
└── assets/             # Supporting files
```
 
## Quality Checklist
 
- [ ] Templates are functional
- [ ] Instructions are clear
- [ ] Formatting is consistent
- [ ] Design is reusable

software-products.md

# Software Products
 
Best practices for SaaS, apps, and AI tools.
 
## Product Types
 
### SaaS/Apps
- Define core value proposition
- Map user journeys
- Define MVP features
- Plan technical architecture
 
### AI Tools
- Define AI capabilities
- Document prompts/flows
- Plan integrations
- Design user interface
 
## Output Structure
 
```text
software-product/
├── prd-lite.md         # Product requirements
├── features/
│   └── feature-1.md
├── user-flows/
│   └── flow-1.md
└── technical/
    └── architecture.md
```
 
## Quality Checklist
 
- [ ] Value proposition clear
- [ ] MVP scope defined
- [ ] User flows documented
- [ ] Technical requirements stated

service-products.md

# Service Products
 
Best practices for productized services and consulting packages.
 
## Product Types
 
### Productized Services
- Define clear deliverables
- Set scope boundaries
- Standardize process
- Create pricing tiers
 
### Consulting Packages
- Define outcomes
- Structure engagements
- Create templates
- Document process
 
## Output Structure
 
```text
service-product/
├── offer.md            # Offer structure and pricing
├── deliverables/
│   └── deliverable-1.md
├── process.md          # Delivery process
└── templates/          # Service delivery templates
```
 
## Quality Checklist
 
- [ ] Deliverables are clear
- [ ] Scope is bounded
- [ ] Pricing is defined
- [ ] Process is documented

Verify Capabilities

Check for optional capabilities that enhance Prodig Suites:

Research Capabilities

Web search tool available (WebSearch, mcp__exa__web_search_exa)
Code graph context available (mcp__CodeGraphContext__*)

Reporting Capabilities

Presentation generation available (paw-tools-presentation)
Release tools available (paw-tools-release)

Note any missing capabilities in the confirmation message. These are optional but enhance the suite's power.

Write Files

Write a temp JSON file with the collected answers structured as {"core": {...}, "module": {...}} (omit core if it already exists). Then run both scripts:

Both scripts output JSON to stdout with results. If either exits non-zero, surface the error and stop.

Run ./scripts/merge-config.py --help or ./scripts/merge-help-csv.py --help for full usage.

Confirm

Display a comprehensive summary:

Then display the module_greeting from ./assets/module.yaml.

Outcome

Output Contract

Once setup completes, the following are guaranteed:

Action type: Module installation/configuration
Files created:
- {project-root}/.pawbytes/prodig-suites/ directory structure
- {project-root}/.pawbytes/prodig-suites/memory/paw-ps-sidecar/index.md
- {project-root}/.pawbytes/prodig-suites/memory/paw-ps-sidecar/curated/*.md
- {project-root}/.pawbytes/prodig-suites/memory/paw-ps-sidecar/curated/product-types/*.md
- {project-root}/.pawbytes/config/config.user.yaml (if core config collected)
Recommendations: Suggest running paw-ps-agent-product-builder to start first product
File saved to: {project-root}/.pawbytes/prodig-suites/*

paw-ps-setup

Documentation

Documentation

Prodig Suites Setup

Overview

Principles

On Activation

Collect Configuration

Create Directory Structure

Create Sidecar Files

1. Create index.md (Orientation File)

2. Create Starter Curated Files

product-context.md

market-intelligence.md

audience-intelligence.md

product-decisions.md

output-standards.md

3. Create Product Type Files

knowledge-products.md

template-products.md

software-products.md

service-products.md

Verify Capabilities

Research Capabilities

Reporting Capabilities

Write Files

Confirm

Outcome

Output Contract

Documentation

paw-ps-setup

Documentation

Prodig Suites Setup

Overview

Principles

On Activation

Collect Configuration

Create Directory Structure

Create Sidecar Files

1. Create index.md (Orientation File)

2. Create Starter Curated Files

product-context.md

market-intelligence.md

audience-intelligence.md

product-decisions.md

output-standards.md

3. Create Product Type Files

knowledge-products.md

template-products.md

software-products.md

service-products.md

Verify Capabilities

Research Capabilities

Reporting Capabilities

Write Files

Confirm

Outcome

Output Contract