@fraylabs/possible 0.1.0 → 0.1.2

package/assets/possible/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: possible
-description: Turn an unclear ambition into a concrete, verified outcome through a short guided conversation, then assemble and run the right reviewed Codex skills after confirmation. Use when the user invokes $possible, asks what they should build or ship, wants help defining an outcome before implementation, or wants a Hardware Launch, Software Launch, or Open-Source Release coordinated end to end.
+description: Turn an unclear ambition into a concrete, verified outcome through a short guided conversation, then assemble and run the right reviewed Codex skills after confirmation. Use when the user invokes $possible, asks what they should build or ship, wants help defining an outcome before implementation, or wants a Hardware Launch, Software Launch, Open-Source Release, or Playable Web Game coordinated end to end.
 ---
 
 # Possible
@@ -31,7 +31,7 @@ Inspect the project read-only when it can answer a question. Do not ask the user
 
 During the brainstorm:
 
-- Do not mention pack names or ingredient skills.
+- Do not mention pack names, lanes, or ingredient skills.
 - Do not create `PRODUCT-BRIEF.md`, `RUN-PROMPT.md`, or `AGENTS.md`.
 - Do not install dependencies, edit files, or spawn subagents.
 - Do not invent facts to make the idea appear more complete.
@@ -42,6 +42,8 @@ After the walkthrough, read [references/packs.md](references/packs.md). If `list
 
 Recommend one primary pack. Use multiple packs only when the user has explicitly described multiple independently valuable outcomes; stage them instead of merging their workstreams.
 
+A lane is catalog browsing metadata, not an intake choice. Do not ask the user to choose a lane; recommend across the complete catalog from the desired finished outcome.
+
 Keep the recommendation compact and conversational. Present:
 
 1. **What I think you want to make** — a brief outcome statement and any material assumption.

package/assets/possible/references/packs.md

@@ -2,10 +2,14 @@
 
 Use this bundled snapshot when the Possible MCP tools are unavailable. Link the recommended pack's public page during the recommendation; disclose its relevant source list and reviewed revisions before installing it.
 
+Lanes are browsing labels only: Create is a first complete usable thing, Launch is a compelling public presentation, Release is evidence-backed readiness to ship or distribute, and Operate is a repeatable ongoing workflow. Do not ask the user to choose a lane; select across the complete catalog from the desired finished outputs. Operate is supported by the model but has no published pack yet.
+
 ## Hardware Launch
 
 Slug: `hardware-launch`
 
+Lane: `launch`
+
 Public page: `https://possible.sh/packs/hardware-launch`
 
 Use for a physical-product idea or prototype that needs one coherent launch presentation.
@@ -41,6 +45,8 @@ Never imply manufacturing readiness, physical validation, certification, or cust
 
 Slug: `software-launch`
 
+Lane: `launch`
+
 Public page: `https://possible.sh/packs/software-launch`
 
 Use for an existing software idea or repository that needs a coherent product release and launch presentation.
@@ -75,6 +81,8 @@ Never imply demand, uptime, security, performance, or production readiness. Depl
 
 Slug: `open-source-release`
 
+Lane: `release`
+
 Public page: `https://possible.sh/packs/open-source-release`
 
 Use for an existing repository that needs a trustworthy, usable release package without publishing it.
@@ -100,6 +108,41 @@ npx skills@1.5.19 add github/awesome-copilot --skill github-release --skill crea
 
 Never imply security, compatibility, production readiness, or release authority. Pushing, tagging, publishing packages, creating releases, and changing repository settings remain separate gates.
 
+## Playable Web Game
+
+Slug: `playable-web-game`
+
+Lane: `create`
+
+Public page: `https://possible.sh/packs/playable-web-game`
+
+Use for a browser-game idea that needs one polished, replayable Three.js experience rather than a general game engine or sprawling feature set.
+
+Outputs: playable browser game, game brief and tuning rules, responsive HUD and controls, production build, evidence report.
+
+Workstreams:
+
+- Core loop and game feel — `game-designer`; owns `game/brief.md` and `game/tuning/`.
+- Three.js game runtime — `threejs`; owns `game/src/`, `game/assets/`, and `game/build/`.
+- HUD and controls — `frontend-design`, `mobile-touch`; owns `game/ui/` and `game/controls.md`.
+- Fresh review — `webapp-testing`; verifies the integrated game with keyboard and touch-sized input paths.
+
+Sources:
+
+- `mrgoonie/claudekit-skills`: `threejs`; reviewed `80113d86bc4407f105af40a2c4ea58194f7c370a`.
+- `dylantarre/animation-principles`: `game-designer`, `mobile-touch`; reviewed `83597134ba8ff59838270f94d7ac7282ffa3b54d`.
+- `anthropics/skills`: `frontend-design`, `webapp-testing`; reviewed `fa0fa64bdc967915dc8399e803be67759e1e62b8`.
+
+Install:
+
+```bash
+npx skills@1.5.19 add mrgoonie/claudekit-skills --skill threejs --agent codex
+npx skills@1.5.19 add dylantarre/animation-principles --skill game-designer --skill mobile-touch --agent codex
+npx skills@1.5.19 add anthropics/skills --skill frontend-design --skill webapp-testing --agent codex
+```
+
+Never imply player demand, accessibility, compatibility, performance, or production readiness beyond direct evidence. Deployment, publishing, analytics, paid assets, and external distribution remain separate gates.
+
 ## Selection rule
 
 Recommend the pack whose finished outputs most closely match the user's desired end state:
@@ -107,5 +150,6 @@ Recommend the pack whose finished outputs most closely match the user's desired
 - Physical product plus launch presentation → Hardware Launch.
 - Software product plus release and launch presentation → Software Launch.
 - Existing repository plus trustworthy public release materials → Open-Source Release.
+- Browser-game idea plus one polished playable build → Playable Web Game.
 
 If none fits, say so. Do not force a pack or invent a new one during intake.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fraylabs/possible",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "description": "Install the Possible Codex skill into a project",
   "type": "module",
   "bin": {