← all publishers

go-sphere

@go-sphere source repo

Report this profile Claim this profile

• 18 skills
• 0 followers
• 6 hours ago last updated

1. ▌
   Prd · go-sphere

   Generate high-quality Product Requirements Documents (PRDs) following go-sphere development workflow. Use when: user wants to create a PRD, document requirements, plan a feature, or translate business ideas into product specs. Required for the PRD solidification phase in AI Agent collaboration development.
   0
   installs
2. ▌
   UX Analyst · go-sphere

   Transform prototype demos from visual representations into behavioral semantics. Use when users provide Figma designs, HTML demos, screenshots, videos, or any UI mockups and need them converted into structured UX flow documents. Trigger on requests like analyze UX, convert demo to flows, write UX-FLOWS, describe user interactions, map screen behaviors, understand page transitions, ux分析, 写 UX 流程, 页面行为分析, 用户流程语义化, or translate prototype to behavior.
   0
   installs
3. ▌
   Spec Writer · go-sphere bundle

   Write or revise implementation-ready specifications for products, systems, APIs, workflows, runtime services, and technical designs. Use when asked to create a new spec from requirements, rewrite an ambiguous PRD or design doc into an executable SPEC.md, deepen an existing specification that feels too thin or hand-wavy, update a spec after scope changes, or modify a specification without leaving contradictions. Trigger on requests such as write spec, rewrite PRD as spec, improve this SPEC.md, make the spec more complete, modify spec, 修改规范, 写技术规格, 改 SPEC, 补技术细节, or 整理实现方案.
   0
   installs
4. ▌
   Interview Me · go-sphere

   Deeply interview the user about technical and product requirements through an interactive, step-by-step decision-tree interview until reaching a shared understanding. Use when planning complex features, architecture changes, API designs, UX refactors, or resolving ambiguous decisions. Enforces exploring the codebase first, asking one question at a time, providing recommended options, and using native interactive question tools.
   0
   installs
5. ▌
   Project Intake · go-sphere

   Organize scattered project inputs and generate standardized intake documents. Use when users mention project kickoff, requirement initialization, PRD preparation, input organization, requirement gathering, or turning prototypes/demos/drafts into structured documents. Apply to new feature development, project initialization, requirement clarification, and similar scenarios. Always complete intake before writing PRD or any detailed design.
   0
   installs
6. ▌
   DB Schema Designer · go-sphere bundle

   Design review-ready database schemas for go-sphere and similar backend projects from requirements, docs, demos, or existing APIs. Use when the goal is to define or review entities, fields, relationships, constraints, indexes, lifecycle states, or schema evolution before any Ent implementation or code generation. Prefer this skill whenever the user wants database design first, review-first modeling, table structure discussion, or approval before coding.
   0
   installs
7. ▌
   Spec Diff Pipeline · go-sphere bundle

   Analyze a changed SPEC or other technical specification from git diff or two version files (v0, v1) and automatically produce downstream planning artifacts such as spec delta, impact map, API/proto delta, schema delta, surface-specific impact reports, task plan, and open questions. Use whenever the user has modified SPEC.md or another design/spec file and wants an AI-run pipeline that reads the diff (either from git or by comparing two version files), traces downstream impact, and prepares implementation-planning markdown outputs for whatever affected surfaces exist in the repo, even if they only say things like 根据 spec diff 分析影响, 刷新 proto/schema 规划, 生成 impact map, 拆 implementation tasks, 分析哪些端受影响, or 对比 v0 v1 版本差异.
   0
   installs
8. ▌
   Sphere Layout Sync · go-sphere

   Update a generated go-sphere project to a newer layout revision, or adopt a legacy project into the layout contract. Use when the user wants to pull upstream layout changes into an existing project, resolve layout drift, set up .sphere/layout.lock.json for a project created before the contract existed, or diagnose why a layout upgrade conflicts. Do not use for ordinary feature work inside a project — that is sphere-feature-workflow.
   0
   installs
9. ▌
   Go Sphere Makefiles · go-sphere bundle

   Standardize, review, or repair Makefiles and Make-driven CI across go-sphere repositories. Use when adding common dependency, formatting, test, lint, check, build, generation, or root batch targets while preserving repository-specific workflows, including multi-module and layout repositories.
   0
   installs
10. ▌
    Go Test Engineering · go-sphere bundle

    Audit, repair, or write Go tests so they enforce real API and behavior contracts. Use for reviewing unreliable or AI-generated tests, removing duplicate or low-value tests, strengthening weak assertions, designing reusable interface contract suites, deciding when golden tests are justified, fixing implementation bugs exposed by valid tests, or adding focused unit and integration tests. Do not use for ordinary Go implementation work that does not involve tests.
    0
    installs
11. ▌
    Proto API Generator · go-sphere bundle

    Design proto3 + HTTP API contracts, including server-streaming SSE endpoints, for go-sphere scaffold projects from prompts, input folders, or requirement docs with mock data. Use when defining service APIs, selecting between entpb/shared/custom messages, and enforcing scaffold conventions, router-safety rules, and service-local error placement. This skill is REQUIRED for any proto API design task in go-sphere scaffold - always use it instead of writing proto files from scratch.
    0
    installs
12. ▌
    Using Sphere Workflow · go-sphere

    Use when the task is in a go-sphere repository, follows the go-sphere delivery lifecycle, or you need to decide which bundled go-sphere skill should run first. This is the bootstrap entrypoint for the sphere-workflow plugin and routes work to the smallest relevant skill.
    0
    installs
13. ▌
    Ent Schema Implementer · go-sphere bundle

    Implement approved database designs as Go Ent schemas for go-sphere projects. Use when the database model has already been reviewed or approved and the next step is to write or update Ent schema code, add entproto annotations, plan generation steps, and wire the schema into bind/render/service integration. Do not use this for early-stage database modeling or review-first discussions; use db-schema-designer first.
    0
    installs
14. ▌
    Ent Seed SQL Generator · go-sphere bundle

    Generate deterministic INSERT SQL seed data from Go Ent schemas and mixed inputs. This skill is REQUIRED whenever you need to create seed SQL for development or testing - it handles entity inference, relationship integrity, stable IDs, and dialect-specific SQL generation including JSON, arrays, and complex types. Use this skill for any task involving seed data, test fixtures, demo initialization, or database population from Ent schema definitions, even if the user doesn't explicitly mention "seed" or "SQL".
    0
    installs
15. ▌
    Proto Service Generator · go-sphere bundle

    Generate or complete unary and server-streaming Go service implementations from protobuf-generated HTTP interfaces in go-sphere scaffold projects. Use when creating internal service files, adding missing method implementations, or generating compilable stubs for new proto endpoints. Trigger for: service implementation, proto handler, SSE producer, append-only update, interface assertion, CRUD via Ent, stub method generation.
    0
    installs
16. ▌
    Sphere Feature Workflow · go-sphere bundle

    Implement end-to-end feature changes in go-sphere scaffold projects by following the layout ownership contract and generation workflow. Use when adding or modifying APIs, protobuf contracts, Ent schemas, bind/map registration, service logic, or cross-layer refactors that must stay protocol-first and avoid manual edits to generated or layout-owned files. This skill is REQUIRED for any task involving go-sphere proto files, Ent schemas, service implementations, or generation commands (make gen/proto, make gen/docs, make gen/wire).
    0
    installs
17. ▌
    Protoc Plugin Engineering · go-sphere bundle

    Write, refactor, or review Go protoc-gen-* plugins in the go-sphere organization. Use when adding a new plugin, changing generated output, reworking plugin config or templates, hardening plugin tests, or reviewing a plugin PR for structure, determinism, immutability, and golden-file discipline. Covers both new-file generators (protoc-gen-sphere, protoc-gen-route, protoc-gen-sphere-errors) and in-place AST rewriters (protoc-gen-sphere-binding). Do not use for authoring .proto API contracts — that is proto-api-generator.
    0
    installs
18. ▌
    Pure Admin Crud Generator · go-sphere bundle

    Generate CRUD pages and router modules for pure-admin-thin from local swagger API definitions. MUST be used whenever you need to scaffold admin list/edit/detail pages, dashboard views, or route configurations from existing API methods in src/api/swagger/Api.ts. This skill replaces manual Vue page creation - use it for any admin panel development task involving API-driven pages.
    0
    installs