chouswei
chouswei/cursor-user-skills
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/chouswei/cursor-user-skills --skill vibe-repo-init命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Keep a working plan as MemNet session rows (campaign or plan task plus ordered step tasks with execution waves). Pin the live neighbourhood, then mutate to draft, update, or repolish. At plan time, mark which steps may run in parallel. Execute a ready wave via memnet-multitask when asked. Chat is a Shape of the graph, never the plan SSOT. Triggers: memnet plan, plan in memnet, update memnet plan, repolish plan, session plan, memnet planner, plan waves, parallel plan steps, execute plan wave. Skip: Markdown-only project-planner interview with no MemNet; building the MemNet engine.
Enforceable MemNet doctrine for Cursor Multitask Mode and Task sub-agents: one shared session SSOT, TCP or streamable-http transport, parent/worker MUST/MUSTNOT, MN-REQ-12 usage, system-dev two-store pattern for modelbasedPrj-*. Triggers: Multitask Mode, multitask, multi-agent, Task sub-agent, background worker, parent coordinator, delegate worker, shared session, memnet multitask, system-dev multitask, modelbasedPrj multitask, MN-REQ-12, parallel workers, TSK_* settle, TCP serve, streamable-http MCP, GQL wire, shaped pin_map.
How to use MemNet as mission working memory: goldfish loop, chat never SSOT, drop prior maps. Triggers: use memnet, how to use memnet, memnet goldfish, mission working memory, chat never SSOT, session graph.
基于 SOC 职业分类
正在显示 SKILL.md
| name | vibe-repo-init |
| description | >- |
Role: Turn a blank (or near-blank) folder into a Cursor vibe-coding basement — runnable skeleton + Cursor project files (AGENTS.md, .cursor/rules/, .cursor/skills/) — for MCU, Linux PC, online server, HTML UI, PC UI, or hybrid mixes.
IDE assumption: Cursor (Agent, project rules, project skills, user-pack skills). Do not scaffold VS Code–only or JetBrains layouts unless the user asks.
Not this skill: full product features, SysML modeling (use SysML hubs), or deep requirements interviews (use project-planner after basement exists).
pipeline_steps in order; do not write files before step 4 OK (unless user waived)..cursor/skills/ is mandatory..cursor/skills/repo-context/ from assets/repo-context-skill-stub.md unless the user names a different first project skill.| Code | Meaning |
|---|---|
mcu | Bare-metal / RTOS firmware (Pico, STM32, …) |
linux-pc | Native Linux/desktop CLI or daemon |
online-server | Hosted API/worker (VPS, PaaS, container) |
html-ui | Browser UI (static or light web app) |
pc-ui | Desktop GUI (native toolkit / Tauri / Electron-class) |
hybrid | Two or more of the above (ordered) |
Full taxonomy: references/repo-types.md.
| Skill | When |
|---|---|
| project-planner | Step 6 — requirements still fuzzy |
| polarfire-soc-setup | MCU/SoC path needs PolarFire kit setup |
| api-client-pattern | Server/client HTTP basement conventions |
| mcp-memnet | Persist @USR scope / @TSK init when serve up |
User-pack skills: ~/.cursor/skills/. Project skills: .cursor/skills/ (required in every scaffold). Route via SKILL-GRAPH.md / repo AGENTS.md. Memory: memnet-goldfish-loop.mdc.