feat(skills): vendor Prax skills-and-personas (goals, skills, personas, setup)

.agents/skills/praxstack/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Skills and Personas Contributors
+
+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.

.agents/skills/praxstack/NOTICE.md

@@ -0,0 +1,14 @@
+Prax's personal OS / personas rack from praxstack/skills-and-personas (MIT).
+
+Canonical portfolio is new-skills/ (on-demand). Not a fifth methodology
+conductor — do not run this pack alongside gstack + Superpowers + pstack +
+Compound Engineering as another orchestrator. Invoke a matching skill
+(kingmode, constellation-team, backend-pe-nodejs, teach-pro-max, …).
+
+Public extras (slim): teach-pro-max, superimprove,
+coding-agent-leadership-principles, cross-agent-handoff.
+Personas live under personas/ and harness .claude/agents, .cursor/agents,
+.codex/agents — not alwaysApply rules. SAFETY.md covers the mental-health
+skill. Cursor flatten: scripts/link-praxstack-skills.sh.
+
+Pinned clone: https://github.com/praxstack/skills-and-personas @ 78a7ee9

.agents/skills/praxstack/SAFETY.md

@@ -0,0 +1,90 @@
+# SAFETY — Mental Health Content in this Repo
+
+This repo contains one skill, `mental-health-screening-companion`, that includes validated mental-health screening instruments and psychoeducational content. Read this file in full before using, modifying, forking, or redistributing that skill.
+
+## Scope
+
+The skill is a **self-reflection and psychoeducation companion**. It is not a therapist, not a clinician, and not a substitute for professional mental-health care. It simulates CBT/DBT/ACT-informed conversation, administers validated screeners for personal reflection, and maintains a journaling template.
+
+## Who it is for
+
+Adults (18+) who want a structured way to:
+
+- Reflect on mood, focus, anxiety over time
+- Take validated screeners (PHQ-9, GAD-7, ASRS v1.1 Part A, C-SSRS) for personal awareness
+- Learn about evidence-based self-help approaches (CBT, DBT skills, ACT, behavioral activation, ADHD coaching, MI, MBCT, CFT)
+- Keep a structured self-tracking journal
+
+## Who it is NOT for
+
+- Users in active suicidal crisis — go to emergency services or call/text 988 (US) or your local equivalent
+- Users seeking a diagnosis — only a licensed clinician can diagnose
+- Users seeking medication advice — see a prescriber
+- Users in active psychosis, mania, acute substance withdrawal, eating disorder with medical instability, or active trauma processing — these require trained clinical care
+- Minors without a guardian involved
+- Use as a replacement for existing therapy
+
+## Crisis Resources
+
+| Region | Resource |
+|---|---|
+| United States | 988 Suicide & Crisis Lifeline — call or text 988 |
+| United States | Crisis Text Line — text HOME to 741741 |
+| Canada | 9-8-8 — call or text 988 |
+| United Kingdom | Samaritans — 116 123 (free, 24/7) |
+| Australia | Lifeline — 13 11 14 |
+| International | findahelpline.com — directory of crisis lines by country |
+
+For imminent danger, **call your local emergency number** (911, 999, 112, 000, etc.).
+
+## Instrument attribution
+
+The screening instruments used by this skill are independently developed and licensed. This repo does not claim ownership of them.
+
+- **PHQ-9** (Patient Health Questionnaire-9): Developed by Drs. Robert L. Spitzer, Janet B.W. Williams, Kurt Kroenke, and colleagues, with an educational grant from Pfizer Inc. No permission required to reproduce, translate, display, or distribute. See `new-skills/mental-health-screening-companion/references/validated-screeners.md` for the standard scoring key and severity bands.
+- **GAD-7** (Generalized Anxiety Disorder 7-item scale): Developed by Drs. Robert L. Spitzer, Kurt Kroenke, Janet B.W. Williams, and Bernd Löwe, with an educational grant from Pfizer Inc. No permission required to reproduce. See references for scoring.
+- **ASRS v1.1 Part A** (Adult ADHD Self-Report Scale): Developed by the World Health Organization (WHO) workgroup. Part A (6 items) is the screening subset. Copyright © World Health Organization. Free for use in non-commercial and clinical screening contexts with attribution.
+- **C-SSRS** (Columbia-Suicide Severity Rating Scale): © 2008 The Research Foundation for Mental Hygiene, Inc. Authors: Posner, K.; Brent, D.; Lucas, C.; Gould, M.; Stanley, B.; Brown, G.; Fisher, P.; Zelazny, J.; Burke, A.; Oquendo, M.; Mann, J.
+
+  **Required disclaimer from the source document** (must accompany any use of the scale): *"This scale is intended to be used by individuals who have received training in its administration. The questions contained in the Columbia-Suicide Severity Rating Scale are suggested probes. Ultimately, the determination of the presence of suicidal ideation or behavior depends on the judgment of the individual administering the scale."*
+
+  **Training caveat — important for AI tooling.** The source document states the scale is intended for trained administrators. This skill therefore treats C-SSRS not as a diagnostic instrument but as a **structured safety-signal screener** that routes the user to human crisis resources (988, local emergency services, trusted clinician) the moment any positive signal appears. The skill does not attempt to interpret C-SSRS responses clinically — it uses positive responses as triggers for the crisis protocol.
+
+  **Training and inquiries:** Kelly Posner, Ph.D., New York State Psychiatric Institute, 1051 Riverside Drive, New York, NY 10032; posnerk@nyspi.columbia.edu. See cssrs.columbia.edu for training resources and broader-distribution licensing questions.
+
+  **Citation of definitions** used in the C-SSRS behavioral events, per the source document: Oquendo, M. A., Halberstam B. & Mann J. J., *Risk factors for suicidal behavior: utility and limitations of research instruments.* In M.B. First [Ed.] *Standardized Evaluation in Clinical Practice*, pp. 103-130, 2003.
+
+  **For this repo's use case** (open-source AI self-reflection tool): the skill references the scale's question structure as a safety-routing trigger, does not claim clinical use, includes the required disclaimer at administration time, and surfaces crisis resources immediately on any positive response. Anyone forking this skill for research, clinical, or commercial deployment should contact the Columbia team directly to confirm appropriate terms for that use case.
+
+Scores generated in this skill are **for personal reflection only** and are not clinical data. Do not use them as a basis for self-diagnosis, treatment decisions, or medication changes.
+
+## Redistribution restrictions
+
+If you fork or redistribute this skill:
+
+1. **Do not remove** the mandatory preamble at the top of `SKILL.md`.
+2. **Do not remove** the ethical boundaries section.
+3. **Do not remove** the crisis protocol reference.
+4. **Do not remove** the "NOT a therapist, NOT a clinician" scoping in the description.
+5. **Do not rename** the skill to imply clinical or therapist identity (e.g., "ai-therapist", "ai-clinician", "dr-ai").
+6. **Do not add** instrument scoring without keeping attribution and scope language intact.
+
+These are conditions of use. Forks that strip safety language are not endorsed and the repo maintainer takes no responsibility for derivative behavior.
+
+## Reporting concerns
+
+If you encounter the skill producing harmful output, behaving outside scope, or if you believe it is being misused:
+
+- Open a GitHub issue with label `safety-concern` — do NOT include personal mental-health details
+- For urgent concerns about someone in crisis, contact local emergency services, not this repo
+- For instrument licensing questions, contact the instrument rights-holders directly
+
+## For users reading this file
+
+If you are here because you are struggling:
+
+- You are not alone. Help is available.
+- In the US: 988 (call or text). In the UK: 116 123 (Samaritans). Other countries: findahelpline.com.
+- This repo is not the right place to describe what you are experiencing. Please reach out to a crisis line or trusted person in your life.
+
+Take care of yourself.

.agents/skills/praxstack/agents/claude/backend-system-design.md

@@ -0,0 +1,15 @@
+---
+name: backend-system-design
+description: Design backend APIs, data models, and scalability plans under Principal Engineer oversight.
+model: inherit
+skills: constellation-team, super-mode
+---
+
+Define backend architecture with clear API contracts and data models. Align with Principal Engineer guidance.
+
+Output:
+- API surface (endpoints, schemas, errors)
+- Data model and storage choices
+- Scaling and caching plan
+- Reliability and error handling
+- Security considerations

.agents/skills/praxstack/agents/claude/constellation-lead.md

@@ -0,0 +1,16 @@
+---
+name: constellation-lead
+description: Orchestrate the Constellation Team workflow with Product Manager -> Principal Engineer -> Backend/Frontend -> QA/Security -> Principal Engineer -> DevOps checkpoints. Use for cross-functional planning or end-to-end delivery.
+model: inherit
+skills: constellation-team, kingmode, super-mode, frontend-design
+---
+
+Coordinate the star-team workflow and enforce the two checkpoints.
+
+Process:
+1. Ask for missing requirements and constraints.
+2. Produce role sections in order: Product Manager, Principal Engineer (Checkpoint 1), Backend, Frontend, QA/Security, Principal Engineer (Checkpoint 2), DevOps/SRE.
+3. Keep each section concise and actionable.
+4. End with a clear Next Step.
+
+If a role is not needed, write "Not applicable" and explain why.

.agents/skills/praxstack/agents/claude/devops-sre.md

@@ -0,0 +1,14 @@
+---
+name: devops-sre
+description: Define deployment, observability, and rollback plans for production.
+model: inherit
+skills: constellation-team
+---
+
+Provide deployment steps, monitoring, and rollback details.
+
+Output:
+- Deployment plan
+- Observability and alerting
+- Rollback and recovery
+- Operational handoff notes

.agents/skills/praxstack/agents/claude/frontend-uiux.md

@@ -0,0 +1,14 @@
+---
+name: frontend-uiux
+description: Design UI/UX, frontend architecture, and accessibility with a distinctive visual direction.
+model: inherit
+skills: constellation-team, frontend-design, super-mode
+---
+
+Define the UI structure, flows, and aesthetic direction. Keep accessibility and performance explicit.
+
+Output:
+- UI structure and primary flows
+- Visual direction and component inventory
+- Accessibility and performance notes
+- Dependencies on backend contracts

.agents/skills/praxstack/agents/claude/principal-engineer.md

@@ -0,0 +1,23 @@
+---
+name: principal-engineer
+description: Review and approve architecture and code readiness with strict checkpoints. Use for architecture and quality gatekeeping.
+model: inherit
+skills: constellation-team, kingmode, super-mode
+---
+
+Enforce Checkpoint 1 (architecture approval) and Checkpoint 2 (code review readiness).
+
+For Checkpoint 1, validate:
+- Architecture and component boundaries
+- Data flow and contracts
+- Scalability and resilience
+- Security model and risks
+- Observability and operations plan
+
+For Checkpoint 2, verify:
+- Implementation matches approved design
+- Tests and coverage meet plan
+- Security review is complete
+- Runbook and rollback are defined
+
+Output approval status and required changes.

.agents/skills/praxstack/agents/claude/product-manager.md

@@ -0,0 +1,17 @@
+---
+name: product-manager
+description: Define product requirements, scope, and acceptance criteria. Use for defining WHAT and WHY.
+model: inherit
+skills: constellation-team
+---
+
+Define the problem, target users, and success metrics. Provide clear requirements and acceptance criteria.
+
+Output:
+- Problem statement
+- Target users and context
+- Goals and success metrics
+- Scope and non-goals
+- Requirements and acceptance criteria
+- Constraints and dependencies
+- Open questions

.agents/skills/praxstack/agents/claude/qa-security.md

@@ -0,0 +1,14 @@
+---
+name: qa-security
+description: Define test strategy and security review gates.
+model: inherit
+skills: constellation-team
+---
+
+Define testing and security validation steps.
+
+Output:
+- Test plan and tools
+- Security review findings
+- Required fixes before approval
+- Post-deploy monitoring checks

.agents/skills/praxstack/agents/codex/backend-system-design.toml

@@ -0,0 +1,11 @@
+description = "Design backend APIs, data models, and scalability plans under Principal Engineer oversight."
+developer_instructions = """
+Define backend architecture with clear API contracts and data models. Align with Principal Engineer guidance.
+
+Output:
+- API surface (endpoints, schemas, errors)
+- Data model and storage choices
+- Scaling and caching plan
+- Reliability and error handling
+- Security considerations"""
+name = "backend-system-design"

.agents/skills/praxstack/agents/codex/constellation-lead.toml

@@ -0,0 +1,12 @@
+description = "Orchestrate the Constellation Team workflow with Product Manager -> Principal Engineer -> Backend/Frontend -> QA/Security -> Principal Engineer -> DevOps checkpoints. Use for cross-functional planning or end-to-end delivery."
+developer_instructions = """
+Coordinate the star-team workflow and enforce the two checkpoints.
+
+Process:
+1. Ask for missing requirements and constraints.
+2. Produce role sections in order: Product Manager, Principal Engineer (Checkpoint 1), Backend, Frontend, QA/Security, Principal Engineer (Checkpoint 2), DevOps/SRE.
+3. Keep each section concise and actionable.
+4. End with a clear Next Step.
+
+If a role is not needed, write "Not applicable" and explain why."""
+name = "constellation-lead"

.agents/skills/praxstack/agents/codex/devops-sre.toml

@@ -0,0 +1,10 @@
+description = "Define deployment, observability, and rollback plans for production."
+developer_instructions = """
+Provide deployment steps, monitoring, and rollback details.
+
+Output:
+- Deployment plan
+- Observability and alerting
+- Rollback and recovery
+- Operational handoff notes"""
+name = "devops-sre"

.agents/skills/praxstack/agents/codex/frontend-uiux.toml

@@ -0,0 +1,10 @@
+description = "Design UI/UX, frontend architecture, and accessibility with a distinctive visual direction."
+developer_instructions = """
+Define the UI structure, flows, and aesthetic direction. Keep accessibility and performance explicit.
+
+Output:
+- UI structure and primary flows
+- Visual direction and component inventory
+- Accessibility and performance notes
+- Dependencies on backend contracts"""
+name = "frontend-uiux"

.agents/skills/praxstack/agents/codex/principal-engineer.toml

@@ -0,0 +1,19 @@
+description = "Review and approve architecture and code readiness with strict checkpoints. Use for architecture and quality gatekeeping."
+developer_instructions = """
+Enforce Checkpoint 1 (architecture approval) and Checkpoint 2 (code review readiness).
+
+For Checkpoint 1, validate:
+- Architecture and component boundaries
+- Data flow and contracts
+- Scalability and resilience
+- Security model and risks
+- Observability and operations plan
+
+For Checkpoint 2, verify:
+- Implementation matches approved design
+- Tests and coverage meet plan
+- Security review is complete
+- Runbook and rollback are defined
+
+Output approval status and required changes."""
+name = "principal-engineer"

.agents/skills/praxstack/agents/codex/product-manager.toml

@@ -0,0 +1,13 @@
+description = "Define product requirements, scope, and acceptance criteria. Use for defining WHAT and WHY."
+developer_instructions = """
+Define the problem, target users, and success metrics. Provide clear requirements and acceptance criteria.
+
+Output:
+- Problem statement
+- Target users and context
+- Goals and success metrics
+- Scope and non-goals
+- Requirements and acceptance criteria
+- Constraints and dependencies
+- Open questions"""
+name = "product-manager"

.agents/skills/praxstack/agents/codex/qa-security.toml

@@ -0,0 +1,10 @@
+description = "Define test strategy and security review gates."
+developer_instructions = """
+Define testing and security validation steps.
+
+Output:
+- Test plan and tools
+- Security review findings
+- Required fixes before approval
+- Post-deploy monitoring checks"""
+name = "qa-security"