All authors
Claude Skills by AruNi-01
github.com/AruNi-0138 skills0 installs119 views
- Atmos Audio GenCreate or revise clean continuous audio beds for Atmos marketing and HyperFrames videos, including cue maps that follow high-density editorial product videos. Use when generating synthetic WAV background music, adding or replacing promo video music, muxing audio into landing page videos, matching audio energy to video beats, or fixing issues like per-scene pause/play, cue-start stingers, chirpy bells, bird-like transition sounds, harsh high frequencies, or mid-track silence.Votes: 0GitHub stars: 6
- Atmos ChangelogRefresh the Atmos landing-page changelog from the GitHub Releases page. Use when Codex needs to read `https://github.com/AruNi-01/atmos/releases`, extract release-note content, and rewrite `apps/landing/src/lib/changelog-data.ts` in the shape expected by the landing changelog UI. Supports generating a specific version on demand, or filling only versions that are still missing from the landing data file.Votes: 0GitHub stars: 6
- Atmos Cli ReleaseRun the standalone Atmos CLI release workflow for this repository. Use this whenever you need to cut an Atmos CLI release, verify `apps/cli/Cargo.toml`, create or dispatch the required `cli-<version>` GitHub Release, and publish CLI archives. Prefer this over local runtime or generic GitHub release flows for CLI releases.Votes: 0GitHub stars: 6
- Atmos Desktop ReleaseRun the Atmos desktop release workflow for this repository. Use this whenever you need to cut an Atmos desktop release, bump the desktop version, create the required `desktop-electron-<version>` tag, push the release-prep commit, and verify the GitHub Actions package flow. Prefer this over a generic GitHub release process for Atmos desktop releases. Publishes the production Electron desktop shell only (Tauri desktop release is deprecated). On packaging CI failure, prefer re-run or same-versio...Votes: 0GitHub stars: 6
- Atmos Docs WriteWrite, improve, restructure, audit, or maintain Atmos user documentation. Use this whenever the user asks to create a new docs page, add a workflow guide, revise concepts or terminology, improve existing docs, refresh docs from code/spec/release evidence, sync bilingual docs, or update `apps/docs/content/docs`. Trigger for phrases like "帮我写 docs", "优化文档", "新增一篇 workflow", "调整概念说明", "发布后更新 docs", "docs for this feature", or "keep docs in sync". Reads existing docs and product evidence first, u...Votes: 0GitHub stars: 6
- Atmos Local Web ReleaseRun the Atmos local web runtime release workflow for this repository. Use this whenever you need to cut an Atmos local web runtime release, verify the local runtime version, create the required `local-web-runtime-<version>` tag, and publish the runtime archives. Prefer this over a generic GitHub release process for Atmos local web runtime releases.Votes: 0GitHub stars: 6
- Atmos Long Task ImplOrchestrate complex multi-file Atmos implementation as the parent lead agent — slice TECH into file-disjoint waves, write a PROGRESS.md kanban, dispatch impl and read-only review subagents, escalate spec gaps to HUMAN, and never write feature code in the parent session. Use when the user asks for parallel implementation, long-task orchestration, kanban-style tracking, wave splitting, dispatch subagents, split a large APP-NNN spec across agents, or when a single atmos-specs-impl session would ...Votes: 0GitHub stars: 6
- Atmos New Pr MergeShip a finished feature or bugfix through a short-lived PR branch with archival history: create a branch from main (or another base), push commits, open a PR using the repo PR template, auto-merge into main, then checkout main and pull latest. Use whenever the user says "new pr merge", "开 PR 并合并", "创建 PR 然后合并到 main", "push 并合并", "leave a PR for the record", or runs /atmos-new-pr-merge. Prefer this over committing or pushing directly to main for routine feature work and bugfixes.Votes: 0GitHub stars: 6
- Atmos Specs BrainstormRun a structured brainstorm for an Atmos spec and write it into `specs/<ZONE>/<ZONE>-NNN_.../BRAINSTORM.md`. Use this whenever the user wants to explore a new feature idea, sketch a rough direction, weigh multiple approaches, or dump unstructured thoughts into the Atmos specs tree — anything that belongs in the BRAINSTORM stage, before a PRD is written. Trigger also when the user says "brainstorm", "头脑风暴", "探索方向", "几种做法", or starts a new `APP-NNN` / `Landing-NNN` / `Docs-NNN` directory. Only ...Votes: 0GitHub stars: 6
- Atmos Specs ImplImplement an Atmos spec — turn the four spec docs (BRAINSTORM / PRD / TECH / TEST) at `specs/<ZONE>/<ZONE>-NNN_.../` into real production code changes in `crates/`, `apps/`, `packages/`. Use whenever the user says "implement APP-NNN", "ship this spec", "按照 spec 实现", "start coding the PRD", or otherwise transitions from spec authoring to actual engineering. Read all four files first, plan along TECH's rollout, respect Atmos's layered architecture (infra → core-engine → core-service → api → app...Votes: 0GitHub stars: 6
- Atmos Specs PrdWrite or update the PRD (Product Requirements) for an Atmos spec at `specs/<ZONE>/<ZONE>-NNN_.../PRD.md`. Use whenever the user wants to lock in WHAT a feature is and WHY it matters — user stories, Must Have / Nice to Have, success metrics, explicit out-of-scope. Trigger when the user says "write a PRD", "产品文档", "需求文档", "定义范围", "user stories", mentions Must Have/Nice to Have, or asks to promote brainstorm output into a PRD. Focus strictly on user value and scope; leave HOW to the tech spec. O...Votes: 0GitHub stars: 6
- Atmos Specs ReviewReview an implemented Atmos spec and write or update `specs/<ZONE>/<ZONE>-NNN_.../REVIEW.md` with actionable post-implementation findings. Use this whenever the user asks to review whether a spec implementation is complete, ready to ship, functionally correct, aligned with PRD/TECH/TEST, or architecturally maintainable. Choose the functional review reference, quality review reference, or both based on the user's wording; if the request is ambiguous or asks for release readiness, use both.Votes: 0GitHub stars: 6
- Atmos Specs TechWrite or update the technical design document for an Atmos spec at `specs/<ZONE>/<ZONE>-NNN_.../TECH.md`. Use whenever the user wants to turn a PRD into a HOW — architecture, data model, API/WebSocket messages, rollout plan, risks. Trigger on "tech spec", "技术方案", "架构设计", "data model", "WebSocket message", "crate layout", or when the user asks how to build a feature the PRD has already pinned down. Respect Atmos's layered architecture (infra → core-engine → core-service → api → apps) and WebSo...Votes: 0GitHub stars: 6
- Atmos Specs Test PlanAuthor the scenario-level test plan for an Atmos spec at `specs/<ZONE>/<ZONE>-NNN_.../TEST.md`. Use whenever the user wants to define WHAT to verify for a feature — Given/When/Then scenarios, acceptance criteria, regression checklist, performance budgets, Playwright/E2E coverage, agent-browser exploratory checks, or manual steps. Trigger on "test plan", "测试方案", "acceptance criteria", "验收标准", "how do we verify", "QA checklist", or after PRD/TECH has stabilized and you need to pin down what "do...Votes: 0GitHub stars: 6
- Atmos Specs Test RunImplement and execute the real tests for an Atmos spec — turn the scenarios in `specs/<ZONE>/<ZONE>-NNN_.../TEST.md` into actual Rust `#[cfg(test)]` modules, `bun test` specs, and Playwright/E2E tests under `e2e/` where warranted, then run them and report. Also run TEST.md-listed agent-browser exploratory checks when the external Agent Browser CLI/skill and local app are available. Use whenever the user says "write the tests", "实现测试", "跑测试", "run the tests for APP-NNN", "make TEST.md actually...Votes: 0GitHub stars: 6
- Atmos Specs ViewThis skill should be used when the user asks for "specs-view", "spec visualization", "visual HTML for BRAINSTORM/PRD/TECH/TEST", "interactive spec review", or a "specs dashboard". It generates a local, single-file interactive HTML view for one Atmos spec file, one full spec, or a current-session/user-specified specs dashboard. It outputs `index.html` plus `metadata.json` under `.atmos/specs/views/` and never scans the whole `specs/` tree unless the user explicitly names the target specs.Votes: 0GitHub stars: 6
- Atmos Video GenCreate or revise premium, product-led Atmos marketing videos and social promo videos using HyperFrames, with an explicit audio generation decision and a strong design/storyboard pass. Use when Codex needs to build, move, render, or maintain video creative projects under marketing/creative, analyze a reference promo video, improve weak creative direction, generate landing-page or X/Threads video assets, decide whether to generate matching audio, sync generated artifacts into app public folders...Votes: 0GitHub stars: 6
- Atmos Web App DeployDeploy the Atmos web app (`apps/web`) to Cloudflare Pages for this repository. Use when the user asks to deploy `app.atmos.land`, publish the web app, or create and push a `deploy-web-app-*` deployment tag.Votes: 0GitHub stars: 6
- Text To LottieCreate, edit, or fix Lottie/Bodymovin JSON animations for the local Skia Skottie player. Use for text-to-Lottie, SVG/logo/type animation, loaders/icons, state feedback, UI microinteractions, lower thirds, diagrams, data/stat/chart animations, product promos, scene/camera motion, visual effects, scene edits, slots/controls, and Skottie debugging.Votes: 0GitHub stars: 6
- AdaptAdapt designs to work across different screen sizes, devices, contexts, or platforms. Ensures consistent experience across varied environments.Votes: 0GitHub stars: 6
- AnimateReview a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight.Votes: 0GitHub stars: 6
- ColorizeAdd strategic color to features that are too monochromatic or lack visual interest. Makes interfaces more engaging and expressive.Votes: 0GitHub stars: 6
- Pt DesignCanonical live-board skill for Atmos Agents: `~/.atmos/skills/.system/atmos-pt-design-agent/SKILL.md` Repo source: [`skills/atmos-pt-design-agent/`](../../../../skills/atmos-pt-design-agent/). Read `document.ptx` (or `pt_ptx_get`), edit the XML, write it back (`pt_ptx_apply` or save the file). Do not invent Excalidraw JSON. Do not start MCP to edit the open Prototype Design tab. Copy prompt from the board includes that skill path. Offline `.ptd` (`document.ptx`, CLI / MCP `--file` only) is do...Votes: 0GitHub stars: 6
- Atmos AutomationFinish an Atmos Terminal or Chat automation run. Read instructions, write final.md, update memory only for durable facts, then call `atmos automation complete`. Not folded into atmos-cli. Do not use for headless process-runner jobs (those complete on process exit).Votes: 0GitHub stars: 6
- Atmos Browser UseControl web pages via Browser Use (`atmos browser-use`), separate from Desktop Use. Prefer for Chrome/Chromium page DOM or Atmos in-app browser (embedded). Do not use for OS window chrome or non-browser apps (Slack/VS Code). No MCP. External path requires Desktop Use control engine 0.19.2+ (extension-free browser tools).Votes: 0GitHub stars: 6
- Atmos Canvas AgentDrive the user's open Atmos Canvas via `atmos canvas` CLI: diagrams, layout, screenshots, local .atmos.tldr documents, and (when needed) durable document scripts or one-shot exec. Use for sketch/draw/diagram/layout requests, and for interactive surfaces or clickable UI only when the user asks for that behavior.Votes: 0GitHub stars: 6
- Atmos CliOperate Atmos product state via the `atmos` CLI (projects, workspaces, terminals, runs, settings, git, headless control). Use when the agent must create or manage Atmos resources without the UI. Do not use for desktop GUI capture/click (atmos-desktop-use), in-page browser DOM (atmos-browser-use), canvas drawing (atmos-canvas-agent), or Device Preview phone (atmos-device-preview).Votes: 0GitHub stars: 6
- Atmos Desktop UseCapture and control the local macOS desktop via `atmos desktop-use` (screenshot, click, type, window list) without MCP. Use whenever the user or task needs local screen capture, UI automation, AppShot-style screenshots, verifying on-screen UI, desktop click/type, or checking Desktop Use install/permissions — even if they say "screenshot the app", "click the button on screen", "drive the UI", or "computer use" on this machine. Do not use for remote machines (Atmos Computer / Relay), Device Pre...Votes: 0GitHub stars: 6
- Atmos Device PreviewControl Atmos Device Preview (iOS Simulator / Android emulator) via `atmos simulator` (screenshot, tap, swipe, type, press) without MCP. Use whenever the user or task needs to tap the simulator, drive an android emulator, interact with device preview, or take a phone screenshot in Atmos. Do not use for macOS desktop capture (atmos-desktop-use) or in-page browser DOM (atmos-browser-use). Not folded into atmos-cli.Votes: 0GitHub stars: 6
- Atmos Pt Design AgentDrive the user's open Atmos Prototype Design board via POST /api/pt-design/agent/invoke: read and edit document.ptx (PTX XML). Use for interactive canvas prototypes. Not Atmos Canvas. Not a wireframe layout engine.Votes: 0GitHub stars: 6
- Atmos Review FixHandle an Atmos review fix run by reading review comments, marking run status with the installed `atmos review` CLI, editing code, replying to each comment, writing a run summary, and finalizing the run into a new review revision.Votes: 0GitHub stars: 6
- Code Review ExpertExpert code review of current git changes with a senior engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements.Votes: 0GitHub stars: 6
- Fullstack ReviewerThis skill should be used when the user asks to review code, review my changes, code review, review this project, check code quality, security review, find bugs, or requests a comprehensive, structured code review covering both frontend and backend.Votes: 0GitHub stars: 6
- Typescript React ReviewerExpert code reviewer for TypeScript + React 19 applications. Use when reviewing React code, identifying anti-patterns, evaluating state management, or assessing code maintainability. Triggers: code review requests, PR reviews, React architecture evaluation, identifying code smells, TypeScript type safety checks, useEffect abuse detection, state management review.Votes: 0GitHub stars: 6
- Git CommitExecute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical groupingVotes: 0GitHub stars: 6
- Project Wiki SpecifyThis skill should be used when the user wants to add a specified topic to the Project Wiki. It generates a focused wiki article on a user-provided theme (e.g., "explore how X feature works", "research why X technology was chosen"), placing it in a dedicated Specify Wiki section separate from Getting Started and Deep Dive.Votes: 0GitHub stars: 6
- Project Wiki UpdateThis skill should be used when the user wants to incrementally update an existing Project Wiki. It detects code changes since the wiki was generated, identifies affected wiki pages, and only regenerates those pages while preserving unchanged content.Votes: 0GitHub stars: 6
- Project WikiThis skill should be used when the user asks to "generate project wiki", "create project documentation", "document the codebase", "generate a wiki for this project", "create docs from code", or wants to produce a comprehensive, navigable documentation set from source code stored locally as Markdown files in `.atmos/wiki/`.Votes: 0GitHub stars: 6