6,348 件 ・ 関連度順
概要と使いどころ
Persistent project goal that survives across sessions and tools, with continuous-execution loop semantics. Use when someone asks to "set a goal", "what is my goal", "goal status", "keep working on X until done", "resume the goal", or wants work to continue across sessions until an objective is achieved. File-backed (.goal.md at project root); shared by every Coco-installed tool working in that repository.
日本語の概要は準備中です。原文の説明を表示しています。
Turn the project you just shipped into a short, polished, shareable launch video (an "ad") using HyperFrames. Use when someone says "/coco-ads", "make a launch video", "brag about this", "turn this into a promo", "make an ad for this", or wants to share what they built. Reads the project code directly — no live URL or screenshots needed. Renders locally.
日本語の概要は準備中です。原文の説明を表示しています。
Weekdays. Checks every project in the inventory from the outside, records one dated observation per project, then reads the production log surfaces since its own cursor and groups every error into a fingerprint so a hundred sightings are one incident. It appends the health ledgers, writes the health digest, and cards the incidents that clear the threshold. It changes nothing, deploys nothing, and never rotates a key.
日本語の概要は準備中です。原文の説明を表示しています。
Weekdays. Takes the one card the standup marked next and turns it into a reviewable change on a branch, never a deployment. It reads the project's own rules and docs first, makes the smallest change the card describes, runs that project's own gate, writes a change brief with the rollback in one line, and pushes the branch for the member to merge. It never merges, never deploys, never applies a migration, and never rotates a key.
日本語の概要は準備中です。原文の説明を表示しています。
Weekly. Works dependency and supply chain debt one project at a time, sorting every candidate into patch and lockfile only, minor, and anything major or breaking. It bumps the first class on a branch behind that project's own gate and pushes it for the member to merge. It holds the other two with a reason and a card carrying the evidence, so the member decides rather than being handed a red build.
日本語の概要は準備中です。原文の説明を表示しています。
How the nWave buddy agent reads a project to answer questions — detection, order of inspection, and citation discipline.
日本語の概要は準備中です。原文の説明を表示しています。
Dung khi muon bien cach team dung AI thanh mot he thong van hanh — Brand Hub lam nguon su that, chia project theo vai tro, skill chain, data loop, nhip review, va bien an toan cho automation gom phan tang hanh dong, tran chi tieu va kill switch. Kich hoat khi user nhac 'AI marketing OS', 'he thong AI marketing', 'Brand Hub', 'setup Claude Project cho team', 'SOP AI team', 'AI moi nguoi dung mot kieu', 'automation marketing co an toan khong'. Khong dung cho — chi can mot output don le thi dung skill tuong ung nhu 00-ke-hoach-mkt hoac 05-copy-quang-cao; setup do luong thi dung skill 53-tracking-setup.
日本語の概要は準備中です。原文の説明を表示しています。
Alive skill router — reads the current project's stack and loads/unloads skills dynamically. Invoke at session start or when project context changes.
日本語の概要は準備中です。原文の説明を表示しています。
Structure Spring Boot 3+ projects with feature packaging and clean layering. Use when structuring Spring Boot 3 projects, defining layers, or applying architecture patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Structure React Native projects with feature-first organization and separation of concerns. Use when structuring a React Native project or applying clean architecture patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Implement Pages Router data fetching with getServerSideProps, getStaticProps, and API routes in Next.js legacy projects. Use when working in a pages/ directory project, adding SSR/SSG data fetching, or creating API routes.
日本語の概要は準備中です。原文の説明を表示しています。
Configure development tools, linting, formatting, and test runners for existing JavaScript projects. Use for ESLint, Prettier, Jest, or equivalent tool setup; defer application implementation and generic project scaffolding.
日本語の概要は準備中です。原文の説明を表示しています。
Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their specific skills.
日本語の概要は準備中です。原文の説明を表示しています。
Project health audit and health check — architecture, performance; Use when assessing overall project health…
日本語の概要は準備中です。原文の説明を表示しています。
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
日本語の概要は準備中です。原文の説明を表示しています。
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
日本語の概要は準備中です。原文の説明を表示しています。
Researches project histories, changelogs, developer interviews, and open source documentation. Use when the album subject involves technology projects or developer stories.
日本語の概要は準備中です。原文の説明を表示しています。
Capture learnings from the current session into the project-rules file (AGENTS.md, CLAUDE.md, or local override) so future sessions benefit. Use when the user says "revise the rules", "update AGENTS.md / CLAUDE.md with what we just learned", "save this to project memory", "remember this for next time", or at the end of a productive session when valuable context has emerged that is not yet documented. This complements agents-md-improver — improver audits, while this one captures.
日本語の概要は準備中です。原文の説明を表示しています。
One full-bleed launch hero in two inks from the project's DESIGN.md: the base color and exactly one brand color, as a slowly folding ordered-dither (Bayer) field — a print/riso look, not a generic gradient. Two flat inks never blend, so there is no mud. The copy sits on a hard-edged base-ink knockout, so headline and sub copy both clear 4.5:1 by construction, and a verify script measures it across the whole timeline. Reads Core v2 tokens (and Google-compatible frontmatter), refuses to invent a palette, ships a CSS halftone poster fallback, respects prefers-reduced-motion, ~7 KiB gzip of library JS. Use for a launch page, product hero, waitlist, event or rebrand first screen that needs motion in brand color. Triggers: '셰이더 히어로', '런칭 히어로', '디더링 배경', '리소 느낌 히어로', '브랜드 컬러 배경 애니메이션', 'dither hero', 'shader hero from DESIGN.md', 'launch hero background', 'riso print hero', 'シェーダーのヒーロー', '著陸頁主視覺 shader'. Whole scroll-native landing → omd-landing / omd-aphrodite. CJK headline ink effect → omd-cjk-type-shader. Brand tokens missing → omd-init first.
One full-bleed launch hero in two inks from the project's DESIGN.md: the base color and exactly one brand color, as a slowly folding ordered-dither (Bayer) field — a print/riso look, not a generic gradient. Two flat inks never blend, so there is no mud. The copy sits on a hard-edged base-ink knockout, so headline and sub copy both clear 4.5:1 by construction, and a verify script measures it across the whole timeline. Reads Core v2 tokens (and Google-compatible frontmatter), refuses to invent a palette, ships a CSS halftone poster fallback, respects prefers-reduced-motion, ~7 KiB gzip of library JS. Use for a launch page, product hero, waitlist, event or rebrand first screen that needs motion in brand color. Triggers: '셰이더 히어로', '런칭 히어로', '디더링 배경', '리소 느낌 히어로', '브랜드 컬러 배경 애니메이션', 'dither hero', 'shader hero from DESIGN.md', 'launch hero background', 'riso print hero', 'シェーダーのヒーロー', '著陸頁主視覺 shader'. Whole scroll-native landing → omd-landing / omd-aphrodite. CJK headline ink effect → omd-cjk-type-shader. Brand tokens missing → omd-init first.
Example template for project-specific skill files covering architecture, patterns, testing, and deployment.
日本語の概要は準備中です。原文の説明を表示しています。
Projeye girdiginde tech stack'i tespit et, uygun skill ve agent'lari aktive et. Kullanim: /project-detect
日本語の概要は準備中です。原文の説明を表示しています。
Security scan, dead code detection, and code quality audit for any project
日本語の概要は準備中です。原文の説明を表示しています。
Create cinematic movie poster concepts and final poster images from a user's brief, existing video plan, storyboard, character design, or project context. Use this skill whenever the user asks to generate a film poster, movie poster, key art, campaign poster, teaser poster, title poster, or promotional visual for a video project. This skill proposes several creative directions first when appropriate, defaults to a 3:4 poster ratio when no ratio is specified, and ensures typography, title treatment, imagery, genre, setting, and story tone are coherent and visually inventive.
日本語の概要は準備中です。原文の説明を表示しています。