「iter」の検索結果

Iteratively review and fix issues on the current branch until the review passes.

日本語の概要は準備中です。原文の説明を表示しています。

Design and review autonomous or semi-autonomous agent loops — systems where an agent prompts itself, runs on a schedule or event, and iterates toward a goal without a human at the keyboard. Use this whenever the user wants to build, design, harden, or audit any kind of self-running agent, agentic workflow, control loop, background worker, cron/heartbeat/webhook-driven agent, "Ralph loop", auto-PR-fixer, monitoring agent, or any long-running task that should keep going on its own until done. Trigger this even when the user says "agentic workflow", "automation that runs itself", "an agent that keeps trying until X", or "make my agent stop running away / burning tokens" without using the word "loop". Also use it to review an existing loop's stopping conditions, guardrails, verification, and escalation paths.

日本語の概要は準備中です。原文の説明を表示しています。

Iterative measurement-driven improvement loop. Measure, profile, mutate, re-measure, commit. Works for performance, bundle size, complexity, test coverage — anything quantifiable. Use when the user wants to systematically improve a metric through repeated cycles of profiling and targeted changes.

日本語の概要は準備中です。原文の説明を表示しています。

Execute git commits using the Conventional Commits specification. Use this skill whenever the user says "commit", "git commit", "/commit", "stage and commit", "make a commit", "save my changes", or asks to commit specific files or all changes. Also triggers on phrases like "push my changes" (commit first), "commit everything", "commit with message X", or whenever git diff/status suggests uncommitted work the user wants to save. Handles auto-staging, diff analysis, message generation, breaking change detection, batch splitting of unrelated changes, safe pushes, and pre-commit hook failures gracefully. Always use this skill rather than ad-hoc git commit commands.

日本語の概要は準備中です。原文の説明を表示しています。

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill to write or revise a README.md for a Shipfox workspace package (libs/*, tools/*). It applies the shared package README standard and repository prose policy. Trigger on write a README, draft README, rewrite README, document this package, or improve the README.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.

日本語の概要は準備中です。原文の説明を表示しています。

技术文档师（多库 Docu）——专注于各类技术文档的编写和维护，包括 README、API 文档、Runbook、架构文档和入职指南。注重清晰度、可操作性和一致性。

日本語の概要は準備中です。原文の説明を表示しています。

报告撰写人（程文成 Cheng）。由 research-chief-editor 主理人在 Phase 4 调度，汇总所有章节通过稿，撰写报告框架部分——深度引言（带引用）、结论（带引用）、目录、APA 格式参考文献列表。输出 JSON。 触发词：由 research-chief-editor 主理人调度执行，不直接面向用户。当所有章节通过审稿后，主理人下发 Phase 4 撰写任务时激活。

日本語の概要は準備中です。原文の説明を表示しています。

文案创作专家（笔澜 · Penn）。擅长公众号/知乎/博客长文写作、小红书/社媒短文案、视频脚本/分镜脚本、营销文案/广告语、SEO 文章优化。 触发词："帮我写一篇公众号长文"、"写一组小红书种草文案"、"帮我写个短视频口播稿"、"写一段产品营销文案"、"帮我起个爆款标题"。

日本語の概要は準備中です。原文の説明を表示しています。

AI 内容创作专家团主理人（司远 · 创意制片人）。协调 6 位专业成员（creative-strategist、copywriter、video-generator、image-creator、video-editor、content-adapter）按预设 Workflow 完成多模态内容生产全流程。 触发词："帮我做个视频"、"生成一段宣传片"、"做一套宣传物料"、"写一篇带配图的文章"、"帮我设计品牌视觉"、"制作短视频"、"内容创作一条龙"。 路由逻辑：单一维度任务走单 Agent 直调；综合性内容需求走对应预设 Workflow。

日本語の概要は準備中です。原文の説明を表示しています。

Reviews integration completeness including design-implementation consistency, review/test coverage, and completion criteria. Use when performing integration review in Construction Phase.

日本語の概要は準備中です。原文の説明を表示しています。

Architect escalation approval — extend iteration limit for a phase that has hit its cap. Records the approval decision in state and allows the blocked transition to proceed.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when routing adversary findings in Phase 4. Provides routing logic, iteration limit enforcement, and escalation protocols.

日本語の概要は準備中です。原文の説明を表示しています。

Run Phase 6 (convergence check) for the active VCSDD feature. Validates four-dimensional convergence: finding diminishment, finding specificity, criteria coverage, and duplicate detection.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when writing sprint contracts in VCSDD strict mode. Provides grading criteria patterns, dimension weight guidelines, and pass threshold formulation for the 5 review dimensions.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when evaluating VCSDD grading dimensions during adversarial review. Provides concrete evaluation checklists for each of the 5 dimensions and convergence signal detection.

日本語の概要は準備中です。原文の説明を表示しています。

Run Phase 4 (feedback routing) after an adversarial review FAIL. Routes adversary findings to the earliest affected phase, checks iteration limits, and escalates to human if limits are exceeded.

日本語の概要は準備中です。原文の説明を表示しています。

Perform a reflective consolidation pass over a hyalo-managed knowledgebase directory — detecting structural issues, fixing broken links, flagging stale content, normalizing metadata, and reporting what changed. Use this skill when the user says /hyalo-tidy, "consolidate the knowledgebase", "clean up the KB", "run KB hygiene", "tidy", or "what needs attention in the knowledgebase". Also use when the user asks about knowledgebase health, broken links, orphan files, stale iterations, or metadata inconsistencies.

日本語の概要は準備中です。原文の説明を表示しています。

Use the hyalo CLI instead of read/edit/grep/write when working with markdown (.md) files that have YAML frontmatter. This skill MUST be consulted whenever pi is working with markdown documentation directories, knowledgebases, wikis, notes, Obsidian-compatible collections, Zettelkasten systems, iteration plans, or any collection of .md files with frontmatter. Trigger this skill when: searching or filtering markdown files by content, tags, or properties; reading or modifying YAML frontmatter; managing tags or metadata across documents; toggling task checkboxes in markdown; getting an overview of a documentation directory; querying document properties or status fields; bulk-updating metadata across many markdown files; or when you find yourself repeatedly using read/edit/grep/write on .md files. Even if the user does not mention "hyalo" by name, use this skill whenever the task involves structured markdown documents with frontmatter. For pi sessions, ALWAYS use `--format text` for compact, LLM-friendly output.

日本語の概要は準備中です。原文の説明を表示しています。

Detect and remove the tells of AI-generated writing in BOTH English and Spanish, and read back the evidence honestly. Use when the user asks to "de-AI" / "humanize" / "un-slop" a draft, to examine whether text carries the tells (delve, tapestry, "it's not just X, it's Y", "here's the thing", em-dash overuse, an assistant's own closing line left in the document), to compare documents for overlap, or mentions signs-of-ai / SignsOfAI. Backed by the SignsOfAI engine — for a measured 0–100 score, sentence-rhythm burstiness, originality, citations, a writer baseline or perplexity, hand off to that engine (web app, CLI or MCP server) as described below. It cannot determine who wrote a text and must never imply that it can.

日本語の概要は準備中です。原文の説明を表示しています。

Use when starting a new feature, product, or system design. Eliminates the spec-implementation gap by making specifications the primary artifact that drives code generation. Keywords: SDD, spec-driven, PRD, feature spec, user stories, implementation plan, specification, acceptance criteria, Given-When-Then.

日本語の概要は準備中です。原文の説明を表示しています。

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

日本語の概要は準備中です。原文の説明を表示しています。