gcwing
- 42 skills
- 0 followers
- 9 hours ago last updated
- ▌ Miniapp Dev 2 · gcwing bundleGenerate and refine OpenBitFun MiniApps. Use when the user wants a new MiniApp, wants an existing MiniApp redesigned or extended, or asks for a OpenBitFun in-app tool. Typical triggers: "做一个小应用", "生成 MiniApp", "写个 OpenBitFun 小工具", "创建 mini app".
- ▌ Product App API · gcwingSparo OS Product App runtime API guidance. Use when writing or reviewing Product App ui.js, worker.js, source_manifest.json, permissions, window.app APIs, app.ai, app.backend service actions, storage, fs/shell/net/os/dialog/clipboard calls, runtime events, or Product App runtime debugging.
- ▌ Lengyi Ppt Agent Team · gcwingDa Ming PPT Agent Team workflow for high-quality deck research, verification, TED 3S outline, visual direction, and assembly. Use when PPT Live or any agent must generate a presentation from a user brief with rigorous sourcing—not template filler.
- ▌ Presentation Director · gcwingDirect one complete evidence-grounded presentation from a minimal topic brief through a frozen Markdown manuscript, Design Case, page-by-page visual production, whole-deck review, systemic revision, and validated PowerPoint export. Use for PPT Live generation and redesign work that needs both content quality and visual quality.
- ▌ Product App Surface · gcwingProduct App surface development guidance. Use when creating, editing, reviewing, or validating an app-private surface, including Product App UI entrypoints, source/index.html, style.css, ui.js, worker.js coordination, primary surface behavior, runtime preview, and user-path evidence.
- ▌ Product App UI Polish · gcwingSparo OS Product App UI polish guidance. Use when improving Product App visuals, layout, runtime UI Kit usage, Sparo OS theme variables, density, empty/loading/error states, accessibility, responsive behavior, light/dark QA, zh-CN/en-US QA, or aligning Product App surfaces with existing built-in app design.
- ▌ Product App Tool Component · gcwingProduct App Tool Component development guidance. Use when creating, editing, reviewing, or validating an app-private Tool Component, including source/tool.schema.json, source/tool.js, structured tool contracts, app or agent calls, deterministic outputs, and capability evidence.
- ▌ Product App Agent Component · gcwingProduct App Agent Component development guidance. Use when creating, editing, reviewing, or validating an app-private Agent Component, including the app's built-in associated agent, prompt.md, fixtures.json, AI behavior, backend bindings, service actions, and Agent Eval evidence.
- ▌ Product App Skill Component · gcwingProduct App Skill Component development guidance. Use when creating, editing, reviewing, or validating an app-private Skill Component, including app-specific workflow knowledge, source/SKILL.md, reusable guidance for the app's agent or authoring flow, examples, and validation evidence.
- ▌ Product App Bridge Component · gcwingProduct App Bridge Component development guidance. Use when creating, editing, reviewing, or validating an app-private Bridge Component, including service action boundaries, source/actions.json, source/worker.js, backend bindings, host or external capability access, permissions, and capability preview evidence.
- ▌ Product App Runtime Component · gcwingProduct App Runtime Component development guidance. Use when creating, editing, reviewing, or validating an app-private Runtime Component, including special Product App hosting requirements, source/runtime.json, execution host boundaries, runtime definition changes, and runtime validation evidence.
- ▌ Miniapp Dev · gcwing bundleDevelops, maintains, and generates OpenBitFun MiniApps (Zero-Dialect Runtime). Use when (1) working on miniapp framework code under src/crates/assembly/core/src/miniapp/ or src/web-ui/src/app/scenes/miniapps/; or (2) generating / creating / designing a NEW MiniApp for the user — including any request like "做一个小应用 / 生成 MiniApp / 写个 OpenBitFun 小工具 / 创建 mini app". Also triggers on MiniApp, miniapps, bridge, zero-dialect, InitMiniApp, app.fs / app.shell / app.storage, or any work under MiniApp/Demo/ and MiniApp/Skills/.
- ▌ Plan · gcwingResearch and write an actionable implementation plan without implementing it. Use when the user asks to plan, design an approach, or inspect a change before coding; stop applying the planning restriction once the user explicitly asks to implement.
- ▌ Debug · gcwing bundleUse this skill to locate a runtime bug. Add targeted instrumentation, collect reproduction evidence, and confirm the root cause before changing code.
- ▌ QA · gcwingSystematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only. (gstack) Voice triggers (speech-to-text aliases): "quality check", "test the app", "run QA".
- ▌ Multitask · gcwingCoordinate multi-part work through parallel subagents when two or more workstreams can proceed independently. Use for decomposable tasks where concurrency materially reduces the critical path; skip for trivial or tightly sequential work.
- ▌ Cso · gcwingChief Security Officer mode. Infrastructure-first security audit: secrets archaeology, dependency supply chain, CI/CD pipeline security, LLM/AI security, skill supply chain scanning, plus OWASP Top 10, STRIDE threat modeling, and active verification. Two modes: daily (zero-noise, 8/10 confidence gate) and comprehensive (monthly deep scan, 2/10 bar). Trend tracking across audit runs. Use when: "security audit", "threat model", "pentest review", "OWASP", "CSO review". (gstack) Voice triggers (speech-to-text aliases): "see-so", "see so", "security review", "security check", "vulnerability scan", "run security".
- ▌ Ppt Design · gcwing bundle使用 HTML 设计与生成高质量演讲幻灯片(PPT/Deck)。当用户希望生成、设计、修改幻灯片、deck、slides、presentation、汇报、提案、pitch、课件时触发。主干:1280×720px 可编辑 HTML 幻灯片 + 唯一 editable HTML→EditableSlideScene→OOXML 管线 + 数据/信息可视化意识 + 5 种设计哲学 + 反 AI slop + 单页自包含 `slide-XX.html`。不生图;缺图用可编辑原语或占位并标注建议补图。
- ▌ Docs Canvas · gcwingRender a documentation-style OpenBitFun Canvas that organizes architecture notes, API references, walkthroughs, runbooks, and how-tos into a navigable layout with sections, tables of contents, diagrams, and cross-references. Use when the user asks for a docs canvas, documentation overview, architecture walkthrough, API reference page, codebase map, runbook, or wants to render structured documentation as an interactive canvas.
- ▌ Find Skills · gcwingDiscover and install reusable agent skills when users ask for capabilities, workflows, or domain-specific help that may already exist as an installable skill.
- ▌ Ship · gcwing bundleShip workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", "merge and push", or "get it deployed". Proactively invoke this skill (do NOT push/PR directly) when the user says code is ready, asks about deploying, wants to push code up, or asks to create a PR. (gstack)
- ▌ Create Agent · gcwing bundleCreate or update OpenBitFun custom modes and subagents. Turn the user's needs into a role prompt and a suitable tool selection, then save an agent definition. Use for reusable roles, not ordinary delegation to an existing subagent.
- ▌ Retro · gcwingWeekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective". Proactively suggest at the end of a work week or sprint. (gstack)
- ▌ Agent Browser · gcwingBrowser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer OpenBitFun's ControlHub browser domain for web automation when it is available; use agent-browser only when ControlHub is unavailable or for supported Electron automation
- ▌ Pre Landing Review · gcwingPre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when explicitly asked for the specialized pre-landing workflow. Product `/review` requests are handled by OpenBitFun's unified Review mechanism instead. (gstack)
- ▌ QA Only · gcwingReport-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead. Proactively suggest when the user wants a bug report without any code changes. (gstack) Voice triggers (speech-to-text aliases): "bug report", "just check for bugs".
- ▌ Writing Skills · gcwing bundleUse when creating new skills, editing existing skills, or verifying skills work before deployment
- ▌ Autoplan · gcwingAuto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with auto-decisions using 6 decision principles. Surfaces taste decisions (close approaches, borderline scope, codex disagreements) at a final approval gate. One command, fully reviewed plan out. Use when asked to "auto review", "autoplan", "run all reviews", "review this plan automatically", or "make the decisions for me". Proactively suggest when the user has a plan file and wants to run the full review gauntlet without answering 15-30 intermediate questions. (gstack) Voice triggers (speech-to-text aliases): "auto plan", "automatic review".
- ▌ Pr Review Canvas · gcwingCreate a OpenBitFun Canvas for reviewing a pull request, branch diff, or change set with Cursor-style diff cards, review maps, risk callouts, and focused reviewer flow. Use when the user asks for a PR review canvas, diff walkthrough, change-set overview, or visual review summary.
- ▌ Agent Eval Canvas · gcwingCreate a OpenBitFun Canvas for single-case agent evaluation and trajectory diagnosis. Use when the user asks to analyze one agent run, trace, case, benchmark item, failure trajectory, eval result, or critical failure step, and wants an incident-review style report covering verdict, step timeline, root cause, error propagation, tool/evidence analysis, efficiency, safety, and repair recommendations.
- ▌ Openbitfun Canvas · gcwing bundleA OpenBitFun Canvas is a live React app that the user can open beside the chat. You MUST use a canvas when the agent produces a standalone analytical artifact — quantitative analyses, billing investigations, security audits, architecture reviews, data-heavy content, timelines, charts, tables, interactive explorations, repeatable tools, or any response that benefits from visual layout. Especially prefer a canvas when presenting structured tool or service results where the data is the deliverable — render it in a rich canvas rather than dumping it into a markdown table or code block. If you catch yourself about to write a markdown table, stop and use a canvas instead. You MUST also read this skill whenever you create, edit, or debug a OpenBitFun Canvas artifact.
- ▌ Investigate · gcwingSystematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively invoke this skill (do NOT debug directly) when the user reports errors, 500 errors, stack traces, unexpected behavior, "it was working yesterday", or is troubleshooting why something stopped working. (gstack)
- ▌ Office Hours · gcwingYC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to "brainstorm this", "I have an idea", "help me think through this", "office hours", or "is this worth building". Proactively invoke this skill (do NOT answer directly) when the user describes a new product idea, asks whether something is worth building, wants to think through design decisions for something that doesn't exist yet, or is exploring a concept before any code is written. Use before /plan-ceo-review or /plan-eng-review. (gstack)
- ▌ Design Review · gcwingDesigner's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use /plan-design-review. Use when asked to "audit the design", "visual QA", "check if it looks good", or "design polish". Proactively suggest when the user mentions visual inconsistencies or wants to polish the look of a live site. (gstack)
- ▌ Create Openbitfun Skin · gcwing bundleInspect the current OpenBitFun Appearance contract and author, repair, package, or validate sparse .openbitfun-appearance skins. Use when Codex needs to discover registered scenes/components/parts/states/facets, check Style IR properties or renderer tokens, initialize or inspect a package, diagnose import failures, verify a skin against a OpenBitFun checkout, or choose a bundled style example for design-specific guidance.
- ▌ Plan Ceo Review · gcwingCEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick expansions), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when asked to "think bigger", "expand scope", "strategy review", "rethink this", or "is this ambitious enough". Proactively suggest when the user is questioning scope or ambition of a plan, or when the plan feels like it could be thinking bigger. (gstack)
- ▌ Plan Eng Review · gcwingEng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when the user has a plan or design doc and is about to start coding — to catch architecture issues before implementation. (gstack) Voice triggers (speech-to-text aliases): "tech review", "technical review", "plan engineering review".
- ▌ Document Release · gcwingPost-ship documentation update. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/AGENTS.md to match what shipped, polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION. Use when asked to "update the docs", "sync documentation", or "post-ship docs". Proactively suggest after a PR is merged or code is shipped. (gstack)
- ▌ Openbitfun Frontend Dev · gcwingSafely customize the running packaged OpenBitFun desktop frontend through a draft, a provisional hot apply, and a 15-second user-confirmed rollback window. Use only in OpenBitFun Creative mode when the user asks to change OpenBitFun's own client UI.
- ▌ Plan Design Review · gcwingDesigner's eye plan review — interactive, like CEO and Eng review. Rates each design dimension 0-10, explains what would make it a 10, then fixes the plan to get there. Works in plan mode. For live site visual audits, use /design-review. Use when asked to "review the design plan" or "design critique". Proactively suggest when the user has a plan with UI/UX components that should be reviewed before implementation. (gstack)
- ▌ Design Consultation · gcwingDesign consultation: understands your product, researches the landscape, proposes a complete design system (aesthetic, typography, color, layout, spacing, motion), and generates font+color preview pages. Creates DESIGN.md as your project's design source of truth. For existing sites, use /plan-design-review to infer the system instead. Use when asked to "design system", "brand guidelines", or "create DESIGN.md". Proactively suggest when starting a new project's UI with no existing design system or DESIGN.md. (gstack)
- ▌ Create Openbitfun Cinematic Wallpaper Skin · gcwing bundleApply the cinematic animated-wallpaper style recipe to a OpenBitFun Appearance skin. Use after loading the parent create-openbitfun-skin Skill when the user provides animated character artwork and wants a host-managed video background, source-derived glass materials, image-led cards, illustrated dialogs, reproducible builds, or cinematic drift checks.