atman-33
- 170 skills
- 0 followers
- 4 repo stars
- last month last updated
- ▌ Global Prompts Sync · atman-33 bundleSynchronizes prompt files (agents, rules, commands) from the skill's prompts directory to both GitHub Copilot and OpenCode global configuration directories. Use when the user wants to update their AI editor prompt libraries.
- ▌ Dbml Multi DB Schema · atman-33 bundleCreate and maintain DBML files for systems that split data across a PrimaryDB and one or more ClientDB instances. Use when adding or updating DBML for multi-database schemas, tenant-specific client databases, cross-database analysis views, logical relationships based on business keys such as ProjectNo, or recommended dbml folder structures.
- ▌ Pr Tech Spec Generator · atman-33 bundleGenerate comprehensive technical specifications from GitHub Pull Requests. Use when users provide a GitHub PR URL and request documentation, technical specs, or change analysis. Analyzes PR commits and diffs using gh CLI and git commands to produce structured documentation covering folder structure, DB schema changes, API definitions, test changes, and dependency updates.
- ▌ Supabase Migration Prep · atman-33 bundleSupabaseデータベースマイグレーションの準備を行うスキル。バックアップの作成と差分マイグレーションファイルの生成を実施します。ユーザーが「マイグレーションを準備」「バックアップと差分を作成」「マイグレーションファイルを生成」などのリクエストをした際に使用します。
- ▌ React Router File Routes · atman-33Reference guide for React Router v7 file-based routing conventions. Use when creating or organizing routes in React Router v7 projects, naming route files, or working with dynamic segments, nested routes, pathless layouts, optional segments, splat routes, and special characters in file-based routing.
- ▌ Permanent Capture · atman-33 bundleCreate and store Obsidian permanent notes under permanent based on user-provided fields (title, summary, domain, kind, topics, status, content). Use when the user says; capture this as a permanent note, add this to permanent, create a hub/leaf/howto/decision/glossary note, or when an agent needs to file structured knowledge into permanent with standardized frontmatter and tags.
- ▌ Acceptance Criteria Drafter · atman-33Creates a draft of Acceptance Criteria for GitHub Issues by interviewing the user about feature requirements and outputting a markdown file in .tmp folder. Triggers on phrases like 'create AC draft', 'draft acceptance criteria', 'write acceptance criteria', or when user wants to define acceptance conditions for a feature.
- ▌ Permanent Rebuilder · atman-33 bundleRebuild and maintain an Obsidian vault's permanent knowledge base for work knowledge and learning notes. Use when asked to reorganize permanent, design hub/leaf/MOC structure, standardize frontmatter (especially required summary), define tag taxonomy, generate a safe restructure plan (dry-run), and apply non-destructive moves/renames while preserving links.
- ▌ Tech Article Humanizer · atman-33 bundleTransform technical article drafts or source materials into human-like, high-quality Japanese technical articles. Use this skill when the user wants to generate, rewrite, or humanize technical articles (especially about TypeScript, JavaScript, React, or frontend topics) following specific human-writing patterns and style guidelines. Triggers include requests like "記事を人間風に", "tech article を生成", "humanize this article", or providing article source materials.
- ▌ Detailed Design Parser · atman-33 bundleParses detailed-design.md files to extract and format file-specific changes for easier copying. Use this skill when the user wants to generate a `detailed-design-by-file.md` from a `detailed-design.md` file.
- ▌ Tech Article Polished Writer · atman-33 bundleGenerate clear, professional, and polished Japanese technical articles suitable for corporate blogs, official documentation, and technical publications. Use this skill when the user wants to create enterprise-level content with consistent polite tone (です/ます), logical structure, and authoritative voice. Triggers include requests like "polished article", "professional tone", "enterprise blog", "公式ドキュメント", "プロフェッショナルな記事", or when content needs formal technical writing.
- ▌ Oh My Opencode Model Switcher · atman-33 bundleSwitch oh-my-opencode.json model configurations between different modes using YAML-based mapping definitions
- ▌ Copilot Agents Ff15 Openspec Serena Sync · atman-33 bundleSync GitHub Copilot agents for FF15-inspired OpenSpec workflow. Team includes Noctis (orchestrator + OpenSpec creator), Iris (issue management), Gladiolus (implementation), Prompto (code quality), Ignis (documentation), and Lunafreya (PR creation). Supports multiple OpenSpec workflows (new, continue, ff, explore, verify).
- ▌ Copilot Agents Ff15 Openspec Non MCP Sync · atman-33 bundleSync GitHub Copilot agents for FF15-inspired OpenSpec workflow (non-MCP version). Team includes Noctis (orchestrator + OpenSpec creator), Iris (issue management), Gladiolus (implementation), Prompto (code quality), Ignis (documentation), and Lunafreya (PR creation). Supports multiple OpenSpec workflows (new, continue, ff, explore, verify).
- ▌ Tasks Md Validation Testing · atman-33 bundleSetup and run comprehensive tests for OpenSpec tasks.md validation. Use when needing to verify validation behavior, create test environments, debug validation issues, or ensure validation works correctly.
- ▌ Tdd · atman-33 bundleTest-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
- ▌ Grill Me · atman-33Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
- ▌ Write A Prd · atman-33Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
- ▌ Pr Assistant · atman-33 bundleAnalyzes git changes and assists with creating comprehensive pull requests. Use when user wants to create a PR, review changes before PR, or needs help drafting PR descriptions. Triggers on phrases like 'create PR', 'make a pull request', 'draft PR description', 'what changed in this branch', 'prepare PR'.
- ▌ Prd To Issues · atman-33Break a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.
- ▌ Write A Skill · atman-33Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
- ▌ Github Release · atman-33Automate GitHub release workflows including version management, CHANGELOG updates, PR creation, and GitHub Release publishing for multi-agent-ff15.
- ▌ Report Writer · atman-33 bundleCreate or update a supplementary report when the user asks レポートにまとめて レポートを作成して report this summarize into a report create a report or write findings to docs/reports.
- ▌ Project Manage · atman-33(opencode-project - Skill) Registers external projects in the FF15 project registry and manages refresh, rename, and delete workflows. Use when registering a new project, re-registering after instruction file changes, renaming a registry entry, deleting a registry entry, or confirming how registry-backed projects are surfaced in the UI. Triggers on: 'register project', 'refresh project metadata', 'rename project', 'delete project', 'project registry', 'project management'.
- ▌ Session Rename · atman-33 bundleRename the current OpenCode session or a specified session using a bundled script when the user asks to change or normalize a session title.
- ▌ Code Simplifier · atman-33Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
- ▌ Openspec Onboard · atman-33Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
- ▌ Openspec Ff Change · atman-33Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
- ▌ Operation Customization · atman-33Create or customize repository operations and facet files. Use when adding or editing builtins/*/operations/*.yaml, jobs, instructions, knowledge, policies, or output-contracts, or when diagnosing operation routing, prompt composition, output placeholders, and debug-preview behavior.
- ▌ Manual Verification Docs · atman-33 bundleOrganize post-implementation manual verification steps, execution methods, and expected results into a checklist-oriented dated Markdown report. Use when the user asks for verification steps, acceptance checks, expected outcomes, or manual test notes for UI, API, job, permission, or notification changes after implementation.
- ▌ Improve Codebase Architecture · atman-33 bundleExplore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.
- ▌ Agent Relationships · atman-33Use when you want a short reference for the relationships and traits of FF15-derived agents such as Noctis, Gladiolus, Ignis, and Prompto.
- ▌ Operation System Contract · atman-33Read this when changing runtime-owned dispatch, source-aware operationRef, step-completion transport, prompt composition boundaries, or live versus debug prompt differences.
- ▌ Operation Authoring And Diagnostics · atman-33Read this before safely changing operation YAML, project workflow authoring paths, source-aware operationRef handling, facet source resolution, output contracts, output placeholders, or workflow-related tests.
- ▌
- ▌ Herdr · atman-33 bundleControl herdr from inside it. Manage workspaces and tabs, split panes, spawn agents, read output, and wait for state changes — all via CLI commands that talk to the running herdr instance over a local unix socket. Use when running inside herdr (HERDR_ENV=1).
- ▌ Writing Great Skills · atman-33 bundleReference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
- ▌ Refine Backlog · atman-33Audit the monday.com backlog for refinement gaps — missing acceptance criteria, missing estimates, oversized or vaguely-titled items — and propose concrete fixes and splits. Use when the user wants backlog refinement/grooming, リファインメント, to check if items are ready for a sprint, or to split a large PBI.
- ▌
- ▌ Zenn Markdown · atman-33This skill should be used when the user asks about "Zenn記法", "Zenn Markdown", "メッセージブロック", "アコーディオン", "埋め込み", "Zenn特有の記法", or mentions writing Zenn articles with specific formatting needs. Provides comprehensive knowledge of Zenn-specific Markdown syntax and best practices.
- ▌ Report Epic Spec · atman-33Generate an HTML report of an Epic's currently-implemented spec and its upcoming planned features, reconciled from the backlog snapshot and the repo's actual state. Use when the user wants a "what exists now vs what's coming" summary, 仕様まとめ, or a feature-status overview for stakeholders.
- ▌ Handoff Go · atman-33 bundleWrite a handoff document and launch the next agent in a split multiplexer pane (herdr or zellij), with new-window and paste-ready fallbacks when no multiplexer is in use.
- ▌ Investigate Spike · atman-33Investigate a spike task from an Epic's backlog using the Epic's dedicated repo clone, and save a findings report the team can decide from. Use when the user mentions a spike, スパイク調査, or wants a technical question from the backlog researched against the actual codebase.
- ▌ Load Epic Context · atman-33Load a PBL Epic's working context — backlog snapshot, repo sync data, and the Epic summary — refreshing stale data first, so the conversation can start from the Epic's current state. Use when the user wants to load/open an Epic, asks "where are we on <Epic>", Epicをロード, or starts a session about a specific Epic's status.
- ▌ Manage Drive Docs · atman-33Search, read, edit, or reorganize (rename/move/delete/list folders) development documentation and its folder structure stored in Google Drive, by accessing the locally synced folder (Google Drive for desktop) directly through the filesystem. Use when the user asks about design docs, specs, or other development documentation kept in Google Drive rather than in the repo, or wants to rename/move/delete files or folders there.
- ▌ Launch Team · atman-33 bundleLaunch a role-based team of Claude Code agents in separate multiplexer panes that coordinate on one task by messaging each other directly.
- ▌ Setup Herdr · atman-33Install herdr (terminal-native agent multiplexer), set up its Claude Code and OpenCode integrations, and configure shell profiles to auto-launch herdr on startup (replacing any existing Zellij autostart block). Use when the user wants to install or configure herdr.
- ▌ Sidekick Go · atman-33 bundleUse when the user explicitly asks to delegate work to a persistent sidekick/helper agent in its own pane that you can iterate with across multiple rounds (e.g. review -> fix -> re-review) without losing its context each time, or when another skill's instructions explicitly direct invoking sidekick-go. Do not use for a one-off review or one-shot subagent task; that's the Agent/Task tool's job.
- ▌ Setup Zellij · atman-33Install Zellij and configure shell profiles to auto-launch Zellij on startup (replacing any existing herdr autostart block). Use when the user wants to install or configure Zellij's shell autostart.
- ▌ Report Pbl Progress · atman-33Generate a PBL Epic's progress & completion-forecast HTML report from its Drive snapshot. Use when the user wants a progress/status report, or a burndown/completion forecast for a PBL Epic.
- ▌ Setup Scrum Context · atman-33Set up or update .claude/scrum-context.json for a project — the monday.com board, Google Drive docs root, and Epic-to-Drive-folder mappings the scrum plugin's other skills and scripts depend on. Use when the user wants to configure monday/Drive settings for a project, or when manage-monday-backlog/manage-drive-docs report no board id or no Drive root configured.
- ▌ Write Retrospective · atman-33Facilitate and record a sprint retrospective for a PBL Epic — prepare sprint facts from the monday.com board, walk the user through Keep/Problem/Try, save the notes to the Epic's Drive folder, and track action items. Use when the user wants a retrospective, ふりかえり/レトロ, or to record what went well and what to improve after a sprint.
- ▌ Commit Changes · atman-33Commit the current changes with a Conventional Commits message. Use when the user asks to commit, or when a workflow (e.g. develop-small-feature) reaches its commit step after implementation is verified.
- ▌ Zenn Blog Writing · atman-33 bundleZennの技術ブログ記事を執筆・編集・レビューするためのガイドラインを提供する。技術的正確性、読みやすさ、AIっぽい文章の排除を重視。Zennの記事(articles/*.md)を書く・直す・レビューするとき、または「Zenn」「技術ブログ」「記事執筆」に言及されたときに使用する。
- ▌ Create Readme · atman-33Create a comprehensive, well-structured README.md for the current project. Use when the user wants to create, write, or refine a project's README.
- ▌ Post To Slack · atman-33Post a message to a Slack channel, resolving channel/user names to IDs and adding an optional @mention or thread reply. Use when the user wants to post, share, or notify something in Slack, or when another skill needs to deliver its output to a Slack channel.
- ▌ Manage Monday Backlog · atman-33Read or update the product backlog on monday.com. Use when the user asks about backlog items, monday.com boards, tickets, or tasks tracked in monday.com.
- ▌ Prepare Sprint Review · atman-33Generate a sprint-review HTML document for a PBL Epic — done items with demo pointers, sprint metrics, and an agenda — from the monday.com board and its Drive snapshot. Use when the user wants sprint review material, a demo agenda, or to prepare for a sprint review / スプリントレビュー.
- ▌ Snapshot Pbl To Drive · atman-33Snapshot a monday.com PBL Epic's items (PBIs), docs, and updates into its mapped Google Drive folder in one script run.
- ▌ Create Work Log · atman-33 bundleCompose a daily or weekly work log from git activity across the user's configured repositories and save it as Markdown (e.g. into an Obsidian vault). Use when the user asks for a work log, daily report, weekly summary, 日報/週報, or "what did I do today/this week".
- ▌ Audit Epic Consistency · atman-33Cross-check an Epic's user stories, PBIs, and acceptance criteria against the actual implementation in its repo, and propose fixes for mismatches, missing/unfinished descriptions, and unclear wording. Use when the user wants a consistency check between backlog and code, 整合性チェック, or asks whether the backlog still reflects what is really implemented.
- ▌ Create Claude Md · atman-33Generate or refine a concise, effective CLAUDE.md for the current project following official best-practice guidelines. Use when the user wants to create, write, or update a project's CLAUDE.md.
- ▌ Wsl Vscode Doctor · atman-33Diagnose and fix `code .` failing to launch, or opening a disconnected Windows-side VS Code instead of a WSL-connected (Remote-WSL) window, in a herdr-spawned WSL shell.
- ▌ Create Pull Request · atman-33 bundleAnalyzes git changes, drafts localized PR titles and bodies, and assists with creating or updating GitHub pull requests for the active agent-harness project repository. Use when working from agent-harness and the user wants to create a PR, review branch changes, draft or update a PR description, or check whether a branch is ready for review.
- ▌ Create Release Notes · atman-33Write user-facing release notes from the Conventional Commits history between two refs — grouped by impact, in plain language, with internal-only changes filtered out. Use when the user wants release notes, an announcement of what's new in a version, or a user-readable summary of changes since the last release (distinct from a developer changelog).
- ▌ Generate HTML Report · atman-33 bundleGenerate a rich, self-contained HTML document instead of a long Markdown file — for specs & plans, PR/code-review explainers, design mockups & prototypes, research/status reports, or throwaway editing UIs. Use when the user asks to write a "report", wants a PR or piece of code explained visually, wants to compare design options, needs a research or status writeup, wants a diagram/flowchart, or when a Markdown plan/spec is getting too long to read comfortably.
- ▌ Manage Desktop Routines · atman-33 bundleCreate, back up, and restore Claude Code Desktop local routines (scheduled tasks) so they survive a PC change. Use when the user wants to set up a recurring or one-off Desktop routine, back up their routines, or restore routines on a new machine.
- ▌ React Router V7 App · atman-33Implements React Router v7 app structure, routing patterns, and component templates. Use when creating or modifying React Router v7 applications to ensure consistent folder structure, data loading patterns, and component architecture.
- ▌ Install Recommended Skills · atman-33Install recommended productivity skills (grill-me, handoff, writing-great-skills) globally via gh skill install.
- ▌ Opencode Log Investigation · atman-33 bundleInvestigates OpenCode runtime errors by locating and analyzing log files. Use when OpenCode fails to start, plugins do not load, MCP servers error out, or terminal shows cryptic errors without details.