liyown
- 26 skills
- 0 followers
- 20 hours ago last updated
- ▌ Img Uploader · liyown bundleUpload and process images, query the shared image library, inspect sync, and preview image-host migrations or Markdown reference repairs with the native img CLI. Use for image hosting and local PNG/JPEG/static WebP processing through configured S3/R2/OSS, GitHub, WebDAV, or HTTP providers.
- ▌ Use Effect · liyown bundleRefactor React code away from direct useEffect usage. Use when Codex needs to review, rewrite, or prevent useEffect in React components, custom hooks, or frontend architecture; diagnose infinite loops or race conditions caused by effects; replace effect-driven state syncing with derived values, event handlers, query libraries, keyed remounts, or a mount-only wrapper such as useMountEffect; or enforce a no-direct-useEffect rule in linting and agent guidance.
- ▌
- ▌
- ▌ Marknative · liyown bundleRender Markdown files to paginated PNG/SVG images using the marknative CLI. Use this skill whenever asked to convert, render, or export Markdown to image formats.
- ▌
- ▌ Mxs CLI · liyownUse when working with `mxs`, `@mx-space/cli`, or a deployed mx-core instance from the terminal. Covers authentication, profiles, safe writes, content CRUD, comments, snippets, AI tasks, preview, and output modes for humans, scripts, and AI agents.
- ▌ Dshx Hub Ops · liyown bundleOperate and maintain DSHX Hub through its stable CLI while using whatever research capabilities are available. Use for adaptive daily, weekly, monthly, or recovery work covering catalog research, sourced bilingual content, local artifact verification, metrics, media, moderation, maintenance, and approval-aware continuation.
- ▌ Dshx Plugin Development · liyown bundleCreate, modify, diagnose, review, package, or Preview-publish an out-of-tree DeepSeek Harness plugin authored with DSHX. Use for @becomeopc/dshx, create-dshx, dshx.config.ts, Host/Client contributions, defineLocale, Prompt, Settings, typed API, Slots, Conversation Components, dshx check/build/dev/inspect/add, and DSH Profile verification. Do not use for DSH core implementation or Framework Hub administration.
- ▌
- ▌
- ▌ Enterprise Stack · liyown bundleUse when an agent needs the full enterprise-dev-flow skill set: language-specific code review (java/react/go/python/node), spec-to-code orchestration (goal-driven-development), durable post-impl knowledge (project-knowledge-capture), doc drift linting (spec-doc-linter), and (planned) data lineage / CODEOWNERS / incident trace / compliance / rollout / RFC / observability skills. Triggers on: 'set up enterprise skills', 'install the full stack', 'enterprise-stack', 'give me the augment', 'what skills should I load', 'superpower-enterprise'. Do NOT use for: a single review (load the matching `*-code-reviewer` directly); a generic TDD/debugging/brainstorming request (use obra/superpowers).
- ▌
- ▌ Data Lineage Trace · liyown bundleUse when you need to prove where a piece of data (PII, PHI, payment data, customer identifier) originates, where it flows through the system, where it lands, and who reads it. Triggers on: data lineage, PII flow, GDPR right-to-erasure, data residency, schema change, retention policy, 'where does field X come from', 'who reads PII column Y', 'walk this field end to end', deletion propagation, audit trail, data classification. Do NOT use for: static code review (use java-code-reviewer, react-code-reviewer, go-code-reviewer, python-code-reviewer, or node-code-reviewer for that), or for design-time brainstorming (use obra/superpowers brainstorming). Complementary to goal-driven-development, which orchestrates the spec-to-code flow; data-lineage-trace is the regulated-data counterpart that runs after a change lands.
- ▌
- ▌
- ▌ Incident Call Trace · liyown bundleUse during a live incident or while writing a postmortem, to walk the call path from a user-facing entry point (HTTP route, queue consumer, cron, CLI) to the persistence layer or external system involved in the failure. Triggers on: incident, outage, postmortem, on-call, SLO breach, 'walk the call path from the route to the DB', 'trace the failing request', 'which service did the timeout come from', runbook, customer impact. Do NOT use for: static code review (use java-code-reviewer, react-code-reviewer, go-code-reviewer, python-code-reviewer, or node-code-reviewer for that), or for local bug debugging (use obra/superpowers systematic-debugging). Complementary to goal-driven-development, which orchestrates the spec-to-code flow; incident-call-trace is the on-call counterpart that walks a live distributed-system failure.
- ▌
- ▌ Cross Team Rfc Draft · liyown bundleUse when a planned change crosses team, service, or product boundaries and needs an RFC, design-doc review, or dependency request before implementation. Triggers on: RFC, design doc, cross-team review, dependency request, shared-kernel change, deprecation proposal, vendor swap, 'I need sign-off from team X', 'this changes a public interface', 'I want to deprecate endpoint Y'. Do NOT use for: design-time brainstorming for a single team (use obra/superpowers brainstorming, then obra/superpowers writing-plans), or for a per-PR review packet (use code-ownership-impact). Complementary to code-ownership-impact, which is the per-PR packet; cross-team-rfc-draft is the long-form RFC that has to be reviewed and signed off by N other teams, each with their own calendar and release train.
- ▌
- ▌ Code Ownership Impact · liyown bundleUse before any change that crosses team or service boundaries, to find CODEOWNERS, blast radius, and required reviewers. Triggers on: rename, refactor, deprecate, schema change, API break, cross-team change, 'who owns this', 'who needs to review', 'what does this PR break', CODEOWNERS, service boundary, dependency request, shared kernel. Do NOT use for: code-review findings (use java-code-reviewer, react-code-reviewer, go-code-reviewer, python-code-reviewer, or node-code-reviewer for that), or for plan decomposition within one team (use obra/superpowers writing-plans). Complementary to goal-driven-development, which orchestrates the spec-to-code flow; code-ownership-impact is the pre-merge counterpart that names the per-team approvers.
- ▌ Compliance Control Walk · liyown bundleUse when you need to demonstrate that a regulatory control (access, audit logging, encryption, retention, consent) actually exists in the running system — not just on a wiki. Triggers on: SOX, ISO 27001, SOC 2, GDPR, HIPAA, PCI, audit, 'show me the audit log for X', 'is PII encrypted at rest', 'who can read this field', 'is consent checked here', control walkthrough, evidence collection. Do NOT use for: a single test-run verification (use obra/superpowers verification-before-completion), or for static code review (use the matching `*-code-reviewer` for that). Complementary to goal-driven-development, which orchestrates the spec-to-code flow; compliance-control-walk is the regulator-frame counterpart that runs against the production-shape behaviour, not the test suite.
- ▌ Goal Driven Development · liyown bundleUse this skill to orchestrate an existing goal or spec through the dev flow. Load when the user asks for end-to-end feature execution, a goal-to-PR pipeline, or any task that crosses spec → implementation → review → knowledge capture. The skill is a thin router: it names the 6 phases (spec intake, blast-radius check, implementation, verification, review gate, knowledge capture) and the skill that does the work for each phase. Do NOT use for: a single review (load the matching `*-code-reviewer` directly), or for a generic author-craft task like TDD / debugging / brainstorming (use obra/superpowers). Complementary to the 17 enterprise-flow skills; for the planned v0.6.1+ skills, the orchestrator names which of them does the work for each phase.
- ▌ Project Knowledge Capture · liyown bundleCapture durable project knowledge after implementation: goals, context, key entrypoints, CodeGraph findings, decisions, verification results, review conclusions, and follow-up notes into docs/knowledge — so the next developer (or the next session) can answer 'why was this done' and 'what to be careful about' in minutes, not days. Use when development completes and project knowledge should be preserved without secrets or process noise. Do NOT use for: chat summaries, raw session transcripts, secrets, customer data, or production data.
- ▌
- ▌ Progressive Rollout Checklist · liyown bundleUse before merging a change that ships behind a feature flag, kill switch, canary, dark launch, or progressive rollout. Triggers on: feature flag, kill switch, canary, dark launch, progressive delivery, rollout plan, 'how do I ship this safely', 'what's the rollback plan', 'is the flag wired up', 'who is in the canary cohort', sunset, deprecation, rollback. Do NOT use for: finishing a branch (use obra/superpowers finishing-a-development-branch), or for post-incident analysis (use incident-call-trace). Complementary to goal-driven-development, which orchestrates the spec-to-code flow; progressive-rollout-checklist is the pre-ship counterpart that verifies the flag, the cohort, the SLO gate, and the rollback path before the change goes live.