sylphxai
24 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
sylphxaiaccessibility-conformance
Assess whether disabled users can complete the selected tasks, and what the current results support saying about conformance. Use when the user asks to review accessibility, audit a conformance claim, or check a VPAT or accessibility statement. Do not use to design the system under review or to fix accessibility defects.
- 導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaianalyze-causal-inference
Estimate a causal effect with an explicit estimand, identification assumptions, design, diagnostics, and sensitivity. Use when the user asks whether a change caused an outcome, for difference-in-differences, IV, or target-trial emulation. Do not use to register a product experiment, forecast an unresolved future event, or critique a present explanation.
- 導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaianalyze-critically
Stress-test a claim, plan, diagnosis, or design by writing rejection conditions before interpreting the evidence. Use when the user asks to critique, steelman, red-team, find the kill criterion, or what would change your mind. Do not use for a domain go/no-go review, a causal effect estimate, a resolvable forecast, or ordinary implementation.
- 導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaianalyze-system-dynamics
Explain behavior over time through stocks, flows, feedback, delays, and adaptive actors. Use for growth, decline, oscillation, bottlenecks, or policy resistance. Do not use to estimate a single causal effect, register an experiment, or forecast a scoreable event without a dynamic structure.
- 導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaiauthor-skill
Write or revise agent-facing instructions: an Agent Skill, CLAUDE.md, AGENTS.md, system prompt, subagent prompt, or reusable prompt. Use when creating a skill, writing a subagent, tightening a trigger, encoding a gotcha, rightsizing CLAUDE.md, or rewriting prompts that still use MUST/NEVER recipes a capable model no longer needs. Do not use for user-facing product copy, store listings, or status updates.
- 導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaibuild-product
Build a missing product capability end to end on a real user path. Use when an accepted direction needs a usable slice across code, interface, data, and delivery, especially when it involves events, webhooks, queues, entitlements, billing state, or sync between systems. Use the product's current identity, storage, job, and event providers; do not invent a second runtime.
- 導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaidesign-offline-sync
Design an offline sync and conflict protocol that preserves user intent across retries, multi-device edits, deletion, and partial failure. Use when offline is a declared product capability. Do not use for ordinary online CRUD or for a live incident.
- 導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaidesign-product-experiment
Turn a product uncertainty into a pre-registered experiment protocol with an estimand, assignment, guardrails, and a decision rule. Use when the result must be able to change a decision. A staged rollout is not automatically an experiment. Do not use to estimate an already-identified observational effect or to run a demo without assignment.
- 導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaidrive-to-delivery
Drive one already accepted engineering or product objective to its requested terminal. Use when completion matters more than a plan. Do not use to choose what to do next from a backlog.
- 導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaifinish-product
Finish an already integrated product to a declared target. Use when the promise is clear and the job is deep resolution of copy, states, feel, and consistency. Do not use to add a capability or to repair a live defect.
- 導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaiforecast-with-calibration
Produce an updateable probability or distribution for a resolvable future event using base rates, explicit assumptions, and a declared resolution source. Use when the user asks for a forecast, probability, confidence, or calibration. Do not use to estimate a past causal effect, register an experiment, or critique a present explanation.
- 導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaigame-product
Design a game product whose promise is play, mastery, fantasy, or progression — loops, systems, feel, and validation. Use when the user asks to design a game, define a game concept, or shape game loops or systems. Do not use for an app, a SaaS web platform, a single UI flow, or a game economy review.
- 導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaihandoff-work
Safely persist in-progress state and write an actionable resumption brief for another machine, session, or developer. Use when handing off work, switching computers or workspaces, pausing mid-task, saving work-in-progress across environments, or transferring an unfinished objective. Also use to write a short status, decision, or incident update that leads with the outcome. Do not use for fully completed deliverables ready to merge (use drive-to-delivery), or production cutovers (use execute-hard
- 導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaimaintain-product
Repair a product defect or regression at its owning layer. Use for live or dogfood failures, flaky paths, and current user harm. Do not use to finish or polish an already integrated product.
- 導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaimodel-product-abuse-risk
Model product abuse and a least-harm control ladder. Use when attackers, fraud, or policy evasion can take money, access, or other users' work. Do not publish an exploitation recipe.
- 導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxainotification-strategy
Assess a notification strategy — stop conditions, cooldowns, cadence, quiet hours, and suppression. Use when the user asks to review notifications, push strategy, or messaging cadence. Do not use to design the notification system.
- 導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaioptimize-decision-model
Translate an operational decision into an explicit model — objective, constraints, uncertainty, and a recomputed solution — then stress it for proxy failure. Use when the user asks to optimize, allocate, schedule, or choose under constraints. Do not use to pick the next backlog item, run an experiment, or critique a claim.
- 導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaiproduce-game-2d-map-assets
Produce engine-ready 2D tilesets, prop packs, layered maps, collision metadata, and composed previews. Use when the user asks for tiles, a tilemap, terrain, Tiled/Godot/Unity 2D maps, or seam-checked atlas props. Do not use for character animation sheets or store key art.
- 導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaiproduce-game-2d-sprites
Produce engine-ready 2D character, VFX, HUD, and icon sprites, including animation sheets and loop QC. Use when the user asks for a sprite sheet, idle/walk/attack cycle, chroma-key frames, video-to-sprite, or a game atlas. Do not use for map tilesets, 3D models, or marketing screenshots.
- 導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaiprototype-product
Run the cheapest real probe that can change a product decision, then kill, continue, or pivot from the observation. Use when the user wants a prototype, spike, or cheap test. A demo without a decision criterion is not this job. Do not use to register a production experiment or to polish an already accepted product.
- 導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxairecord-structured-deliberation
Structure a multi-participant deliberation and record a decision-ready result — options, strongest reasons, dissent, and the named owner's next action. Use when several perspectives, competing proposals, or material objections need a fair synthesis. Do not use for a single-analyst critique or a domain go/no-go review.
- 導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxairesolve-customer-support-case
Resolve one customer support case through a truthful outcome, authorized action, and verified closure. Use for a single ticket, not for designing the support system.
- 導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxairun-product-feedback-loop
Cluster support tickets, in-app feedback, and authorized store reviews into owned product work and close the loop with the people who wrote in. Use when triaging feedback, mining reviews, or asking what customers said after a launch. Do not use to answer one ticket.
- 導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日
sylphxaiui-flow
Design or implement one product UI flow with loading, empty, error, and success states, verified on a real render. Use when the user asks to build a screen, fix a form, design a flow, or match an existing design system. Do not use to review an existing flow, extract a design system, or produce store screenshots.
- 導入数
- 1
- GitHub Stars
- 2
- 更新日
- 10月3日