「new」の検索結果

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and scope, or when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single requirement spans several independently testable capabilities and needs decomposing into a capability map of modules before specifying.

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

When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.

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

Hardens code against vulnerabilities. Use when auditing an input handler for vulnerabilities, when handling user input, authentication, data storage, or external integrations, or when checking a login flow is safe against the OWASP Top Ten. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services. Use when auditing dependencies for known vulnerabilities, triaging package-manager audit findings, or assessing supply-chain risk in a new package. Use when personal data or privacy compliance (GDPR, CCPA) is involved.

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

Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or eslint-disable suppressions, skipped or deleted tests, assertions stripped out, unimplemented stubs, thresholds edited down. Use when no quality bar is written down, when the user says "set up constraints" or "define our standards", when the user wants dimensions they care about — accessibility, web performance, coverage — set up as enforced constraints, when an agent keeps silencing checks or skipping tests to get to green, when you need a coverage or performance threshold and don't know what number to pick, or when an agent writes more code than anyone will read.

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

Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.

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

When the user wants to edit, review, or improve existing marketing copy, or refresh outdated content. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' 'copy sweep,' 'tighten this up,' 'this reads awkwardly,' 'clean up this text,' 'too wordy,' 'sharpen the messaging,' 'refresh this content,' 'update this page,' 'this content is outdated,' or 'content audit.' Use this when the user already has copy and wants it improved or refreshed rather than rewritten from scratch. For writing new copy, see copywriting.

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

Use for Korean (Hangul) fan translations of retro console or PC games, including ROM or disc analysis, text-engine reverse engineering, Hangul fonts and custom encodings, script extraction and reinsertion, code hooks, reproducible product builds, and emulator verification. Apply it to new investigations and follow-up work in existing Korean-patch projects. 레트로 게임 한글화·한글패치·한글 패치·ROM 번역의 신규 조사와 기존 프로젝트 후속 작업에 사용한다.

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

Create and manage tickets — initiatives, epics, stories, bugs. Use when the user says "create a new initiative", "slice this initiative", "split this epic up", "break this into stories", "incept this epic", "make a ticket", "refine this ticket", "what's ready", "status of a story", "publish ticket changes", "validate these tickets", "set up the ticket store".

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

Overview of the Neon platform for apps and agents, spanning Postgres, Auth, Data API, and the new services: Object Storage, Compute Functions, and AI Gateway. Use whenever "Neon" is mentioned for an overview of how to work with Neon and how to get started. Otherwise, the individual capabilities are the triggers: "object storage" or "S3-compatible storage", "serverless functions", "background jobs", or "run code near my database", "AI gateway", "LLM proxy", "model routing", or "call an LLM" → AI Gateway; "database", "Postgres", or "authentication" → Postgres and Auth.

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

Environment-aware pre-flight check. Use when starting work in a new environment, switching machines, or when 'works on my machine' bugs surface. Validates OS, runtime versions, installed tools, port availability, env vars, and disk space BEFORE coding starts. Like sentinel but for the environment, not the code.

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

Scan market trends, competitor activity, and emerging patterns. Monitors Product Hunt, GitHub Trending, HackerNews, and social platforms.

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

Use when creating new Rune skills, editing existing skills, or verifying skill quality before deployment. Applies TDD discipline to skill authoring — test before write, verify before ship.

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

Business Analyst agent. Use when starting a new feature requiring requirements elicitation BEFORE plan or cook. Asks probing questions, identifies hidden requirements, maps stakeholders, defines scope boundaries, and produces a structured Requirements Document that plan and cook consume.

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

Verify AI-generated imports, API calls, and packages actually exist. Use when finishing AI-generated code that introduces new imports or external API calls — auto-fires after fix/cook to catch phantom functions, non-existent packages, and slopsquatting attacks.

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

Auto-generate project context for AI sessions. Use when starting on a new repo for the first time, or when CLAUDE.md / .rune/ context is missing or stale. Scans codebase and creates the setup so every future session starts with full context.

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

Use whenever the user mentions Zenodo, depositing or publishing research artifacts (datasets, software, papers, posters) to Zenodo, minting a DOI for a dataset/code release, uploading files to a Zenodo record, creating a new version of a Zenodo deposit, or searching Zenodo records. Covers the full Zenodo REST API workflow — create deposition, upload files via the bucket API, set metadata, publish, version, and search — for both production (zenodo.org) and sandbox (sandbox.zenodo.org).

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

Socratic tutor that teaches codebase understanding through questioning, challenges, and active recall. Invoke with /learn-codebase when onboarding to a new codebase or deepening understanding of existing code. Maintains a learning journal that tracks mastery and schedules reviews.

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

Generate minimal, abstract, UI-inspired illustrations for software product features — as deterministic SVG. Use when asked for a feature illustration, product illustration, spot illustration, empty-state graphic, feature-card artwork, docs or developer-portal illustration, or a consistent illustration set/family for a product. Also use to turn a feature description or a product screenshot into an abstract UI illustration, to add a new illustration to an existing family, or to retheme an existing set.

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

Marketing playbook for open-source projects led by non-technical founders. Covers README optimization, community building, contributor attraction, and translating OSS traction into revenue. By @WeiYipei.

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

Design and execute a 14-day GitHub repository growth sprint using README conversion, competitor-window research, Reddit, Hacker News, launch directories, community activation, and contributor loops. Use when launching an open-source repository, diagnosing weak star conversion, or building sustained GitHub discovery without buying stars.

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

🇺🇸 Open-Source Marketing & GitHub Stars Growth System — Decision framework for each growth stage. Pre-launch readiness → Show HN / Reddit / Product Hunt launch → 6-month growth loop. README rules, KOL outreach, dev-content matrix (dev.to / Zenn), anti-star-farming. Built from taking AFFiNE 0 → 60K stars. 🇨🇳 开源营销与 GitHub Star 增长系统 — 每个增长阶段的决策框架。Pre-launch 就绪 → Show HN / Reddit / Product Hunt 发布 → 6 个月增长循环。README 规则、KOL 合作、开发者内容矩阵（dev.to / Zenn）、防刷 star。提炼自 AFFiNE 0 → 60K star 实战。 🇯🇵 オープンソースマーケティング＆GitHub スター成長システム — 各成長段階の意思決定フレームワーク。Pre-launch → Show HN / Reddit / Product Hunt → 6ヶ月成長ループ。READMEルール、KOL連携、開発者コンテンツマトリックス。 🇰🇷 오픈소스 마케팅 & GitHub 스타 성장 시스템 — 각 성장 단계별 의사결정 프레임워크. 사전 출시 → Show HN / Reddit / Product Hunt → 6개월 성장 루프. README 규칙, KOL 아웃리치, 개발자 콘텐츠 매트릭스. Triggers: "open source marketing" | "GitHub stars" | "star growth" | "Show HN" | "Hacker News launch" | "OSS launch" | "developer marketing" | "Reddit launch" | "dev.to" | "open source growth" | "开源营销" | "GitHub star 增长" | "开源发布" | "Show HN 怎么发" | "开发者营销" | "オープンソース" | "오픈소스 성장"

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

Twitter/X Agent Operations SOP v2 — Rebuilt from real dual-account operations. Real data: • CN account: grew from 1,150 → 3,679 followers (~14 months), 1 tweet/day, OAuth1 direct post • EN account: Buffer API • Real incidents: cron silent-failed for 2 weeks unnoticed, analytics data off by 17×, thread performance worse than single posts What's new in v2: • Step-by-step onboarding (Q1→Q6), multiple choice wherever possible — no big forms • Mandatory daily log after every tweet + weekly report every Monday • Pre-publish safety checklist (agent must pass before posting) • Content pool tracker (used/unused) + alert when ≤3 items remain • Dual-account credential separation (CN: OAuth1 / EN: Buffer API) • MASTER-STATUS.md as the single source of truth — read + write every session 🇨🇳 Twitter/X Agent 运营 SOP v2 — 基于真实双账号运营经验重写。 开局对话式收集 context、强制日报+周报、发推前红线自检、素材库追踪、双账号凭证分离、MASTER-STATUS.md 单一真相来源。 真实数据：中文账号从 1,150 粉增长至 3,679 粉（约14个月），1条/天。 Triggers: "twitter运营" | "推特agent" | "发推SOP" | "AI代运营" | "推文日报" | "素材库" | "Buffer API" | "OAuth1发推" | "twitter automation" | "tweet sop" | "推特涨粉"

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

Resolves stuck review findings via a put-up-or-concede exchange. Invoked by the facilitator when a finding survives arbitration without new evidence.

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

GPS-aligned genealogical research assistant for family history, ancestor research, record analysis, source-information-evidence classification, conflict resolution, citations, FAN research, privacy-sensitive document analysis, and proof statements, summaries, or arguments. Use for census, vital, probate, land, military, church, newspaper, DNA-plus-documentary, and other genealogy evidence tasks. Not for GEDCOM creation (use gedcom-creator), general history questions, DNA-kit shopping, or generic writing tasks.

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