- Skills
- 650
- 仓库
- 1
- 职业覆盖
- 10
- 场景覆盖
- 7
- Stars
- ★ 23
monoes 的 Skills 650
zk-steward
Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.
writing-plans
Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.
write-spec
Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.
write-query
Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.
workflow-automation
Org role guidance for workflow automation: build and maintain CI/CD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.
workflow-architect
Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.
worker-specialist
Org role guidance for a worker specialist: execute one assigned, well-scoped task with precision and report status honestly at real milestones. Covers confirming done-criteria first, surfacing blockers immediately and sharing intermediate results with peers.
win-loss-review
Analyze recently closed opportunities to find patterns in what wins and what loses - stage of loss, common objections from transcripts, deal characteristics. Leader-focused. Use when the user asks "win loss review", "why are we losing deals", "what's working", or "analyze closed opps".
weekly-wrap
End-of-week summary for a rep or leader - what closed, what moved, what slipped, and what's on deck Monday. Optionally drafts a chat post to the team channel. Use when the user says "weekly wrap", "week in review", "what happened this week", or "Friday summary".
weekly-prep-brief
Generate a comprehensive weekly briefing for all external calls in the next 7 days. Triggers on 'weekly prep brief', 'prepare my week', 'what calls do I have this week', 'Monday prep', or any weekly planning request.
vue-patterns
Use when building or reviewing Vue 3, Nuxt or Pinia code and want idioms: Composition API, project layout, reactivity, Vue Router and SSR. A pattern catalogue; for full builds including Quasar mobile and PWA see vue-expert.
vue-expert
Use when building Vue 3 apps end to end: Composition API components, Nuxt 3 SSR/SSG, Pinia stores, Quasar/Capacitor mobile, PWA and Vite build tuning. Persona with reference files and vue-tsc and Vitest validation. For a catalogue of Vue idioms see vue-patterns.
visual-design-foundations
Use when establishing design tokens or a style guide: typography scales, color palettes, 8-point spacing, iconography and visual hierarchy. Includes CSS token examples, accessible contrast and dark mode theming.
visionos-engineer
Use when an org role acts as visionOS engineer and must build Vision Pro spatial apps with SwiftUI, RealityKit and ARKit: windows, volumes, immersion. Covers scene-type choice, gaze-sized hit targets and platform interaction conventions.
view-pdf
Interactive PDF viewer. Use when the user wants to open, show, or view a PDF and collaborate on it visually — annotate, highlight, stamp, fill form fields, place signature/initials, or review markup together. Not for summarization or text extraction (use native Read instead).
verification-before-completion
Use when about to claim work is complete, fixed or passing, before committing or opening a PR: run the verifying command and read its output first. Gate function of identify, run, read, verify, then claim, with a table of what evidence each claim needs.
vendor-review
Evaluate a vendor — cost analysis, risk assessment, and recommendation. Use when reviewing a new vendor proposal, deciding whether to renew or replace a contract, comparing two vendors side-by-side, or building a TCO breakdown and negotiation points before procurement sign-off.
vendor-check
Check the status of existing agreements with a vendor across all connected systems — CLM, CRM, email, and document storage — with gap analysis and upcoming deadlines. Use when onboarding or renewing a vendor, when you need a consolidated view of what's signed and what's missing (MSA, DPA, SOW), or when checking for approaching expirations and surviving obligations.