8,533 件 ・ 関連度順
概要と使いどころ
Rename a thesis file when company name changes. Atomically updates filename, all inbound wikilinks across the vault, graph adjacency entry header, sector note Active Theses entry, snapshot snapshot_of references, and _hot.md mentions. Use when company changes name (FB → META, Square → Block, etc.), or when correcting a typo in a thesis filename.
日本語の概要は準備中です。原文の説明を表示しています。
Tag a thesis's implicit macro bets — the macro variables its bull case is secretly levered to (AI capex, rates, FX, China decoupling, memory/HBM cycle, energy, regulation) with direction and magnitude. Use when user says "macro exposure", "what macro is [TICKER] betting on", "macro bets", or "rate exposure for [TICKER]".
日本語の概要は準備中です。原文の説明を表示しています。
Restore a thesis, sector, or macro note from a snapshot in _Archive/Snapshots/. Use when user says "rollback", "restore", "revert", "undo sync", or "go back to the previous version".
日本語の概要は準備中です。原文の説明を表示しています。
Synchronize recent research learnings across all affected theses, sector notes, and macro documents. Use after a research session or when user says "sync", "propagate", or "update everything".
日本語の概要は準備中です。原文の説明を表示しています。
A modern, graphic, editorial-poster aesthetic — warm and confident — built on alternating cream and burnt orange sections, an amber brand color.
日本語の概要は準備中です。原文の説明を表示しています。
A playful, joyful, two-color risograph print aesthetic built on a single warm off-white paper surface running through every section
日本語の概要は準備中です。原文の説明を表示しています。
Magazine-grade, collage-driven editorial system: warm paper canvas, surreal plaster-and-architecture imagery, oversized display type, hairline rules, and Roman-numeral section markers.
日本語の概要は準備中です。原文の説明を表示しています。
A clean, product-oriented default. Use when the brief doesn't call for a specific mood — good for B2B tools, dashboards, and utility pages. Content-first, chrome-second.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a single-file product landing page with a layered ASCII cosmos hero (rotating ASCII planet, drifting irregular asteroids, comet trails, nebula gas clouds — each in its own harmonious color) plus full marketing sections (about / features grid / showcase / spec / pricing / CTA / footer). Takes a natural-language description of one product (any kind — a note app, a coffee subscription, a CLI tool, an indie hardware, a hosting service…) and outputs ONE working .html file with deep-space dark or warm-letterpress theme. Runs in BOTH Claude Code (writes to ~/Desktop) and GLM / online chat (outputs HTML inline). Trigger phrases: "做个宇宙风产品落地页", "生成 ASCII 产品官网", "ascii-cosmos-gen ...", "做个独立软件 / 独立硬件落地页", or when user drags this skill folder into chat asking for an atmospheric product landing page.
日本語の概要は準備中です。原文の説明を表示しています。
Canonical UI/UX best practices ruleset with 14 sections and 70+ rules prioritized P0–P3. Use when implementing, reviewing, or auditing UI components. P0 rules are mandatory — violations are bugs. All rules reference tokens from ui-theme-reference.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants a code review of an explicit range or set of files — correctness, security, performance, conventions, tests — with stable findings (CR-nnn, BLOCKER..INFO) and rule citations — 'revisar os últimos commits', 'code review da feature X', 'review base..HEAD'. Plans a REPORT-mode review (no code changes, no commit). Do NOT use to fix code (feat-feature / feat-quick), to write tests (feat-test) or for UI/UX design critique.
日本語の概要は準備中です。原文の説明を表示しています。
Copy para setor público e saúde — linguagem cidadã, acessibilidade, LGPD e comunicação de política pública. Use quando o contexto for prefeitura, secretaria, SUS, assistência social, transparência ou governo digital, ou quando o usuário citar DashSaúde, Integra Arapiraca, ODARA, e-SUS ou APS.
日本語の概要は準備中です。原文の説明を表示しています。
Arquitetura e diagnóstico AWS — VPC, EC2, ECS, EKS, ALB, NLB, RDS, ElastiCache, S3, CloudFront, Route53, IAM, WAF, GuardDuty. Use quando o usuário disser "AWS", "VPC", "ALB", "RDS", "revisar a arquitetura", "Well-Architected", "subnet", "security group", "IAM", ou citar qualquer serviço AWS. Leitura livre; qualquer mudança passa pelo portão de confirmação.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnóstico e operação de Kubernetes — pods, deployments, ingress, HPA, PVC, StorageClass, NetworkPolicy, Secrets, Helm, ArgoCD, cert-manager. Use quando o usuário disser "kubernetes", "k8s", "pod", "deployment", "ingress", "CrashLoopBackOff", "não sobe", "escalar", "helm", "argocd". Leitura livre; apply, scale, delete passam pelo portão.
日本語の概要は準備中です。原文の説明を表示しています。
Write and refine high-quality user stories — INVEST criteria, "As a X, I want Y, so that Z" format, Gherkin acceptance criteria when applicable, definition of ready, anti-patterns, and a review checklist. Use when creating or reviewing user stories, PRD section 6, backlog items, or acceptance criteria. Do NOT use for technical specs, architecture decisions, or task decomposition.
日本語の概要は準備中です。原文の説明を表示しています。
Segundo cérebro persistente em Markdown — LLM Wiki no padrão Karpathy mantida como bundle Open Knowledge Format v0.2, com fontes imutáveis em raw/ e conceitos citados em wiki/. Use quando o usuário disser "segundo cérebro", "second brain", "adiciona isso ao meu brain", "salva na minha wiki", "ingere esse artigo/PDF/link", "o que minha wiki diz sobre", "o que meu brain sabe sobre", "consulta meu conhecimento", "lint da wiki", ou pedir para acumular conhecimento de fontes de forma durável. NÃO use para notas do Obsidian (pwdev-obsidian), planejamento de features (pwdev-feat) nem PRDs (pwdev-prd).
日本語の概要は準備中です。原文の説明を表示しています。
Create professional, dark-themed architecture diagrams as standalone HTML files with SVG graphics. Use when the user asks for system architecture diagrams, infrastructure diagrams, cloud architecture visualizations, security diagrams, network topology diagrams, or any technical diagram showing system components and their relationships.
日本語の概要は準備中です。原文の説明を表示しています。
Implement React Server Actions in Next.js 14+ for secure, progressively enhanced form handling and server mutations without API routes. Use when handling form submissions, performing server-side mutations, implementing progressive enhancement, creating actions that work without JavaScript, validating data on the server, revalidating cached data after mutations, handling file uploads server-side, implementing optimistic UI updates, or building forms that gracefully degrade without client-side JavaScript.
日本語の概要は準備中です。原文の説明を表示しています。
Two-phase memory hygiene. Phase 1: scan external Claude Code memory (~/.claude/projects/<slug>/memory/) for durable rules to migrate into the repo and entries already duplicated by repo atoms. Phase 2: audit in-repo memory/, CLAUDE.md, docs/architecture/, and docs/sections/ for dead links, duplication, drift, and bloat.
日本語の概要は準備中です。原文の説明を表示しています。
Stryker-driven test cull: delete slop, consolidate redundants, fill mutation-coverage gaps. Score up, test count and lines down. Use when the user says 'trim tests', '/trim-tests', or wants to clean up LLM-generated test bloat. No args picks the worst-scored file; argument scopes to a section, service, or file.
日本語の概要は準備中です。原文の説明を表示しています。
Autonomous themed tech-debt cleanup. Reads docs/architecture/debt-ledger.yml, rotates to the least-recently-served debt theme, works it for a time budget (default 2h) or until drained, opens one PR, and asks judgment questions inline at the end. Use for daily debt burndown without Peter pointing at a target: grandfathered analyzer rules, architecture-test baselines, obsolete-field reads, cross-section stitching.
日本語の概要は準備中です。原文の説明を表示しています。
Autonomous Reforge-guided refactor workflow for the Humans repository. Use when the user wants Codex to target a section such as Shifts, Users, Teams, Tickets, Camps, or Store, create a dedicated worktree/branch from origin/main, run iterative architecture-focused improvements, score each stage with Reforge, gate commits through a score-blind read-only architecture review, append score and verdict details to commit messages after review acceptance, push progress, and open a PR when the loop reaches stasis.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see email-sequence. For popup copy, see popup-cro. For editing existing copy, see copy-editing.
日本語の概要は準備中です。原文の説明を表示しています。
Provide advisory guidance for the Adobe Dispatcher Apache HTTP Server module and related HTTPD configuration in AEMaaCS cloud workflows only, with public-doc citations and cloud-specific MCP verification plans. Use for conceptual questions such as `statfileslevel`, filter rules, URL decomposition, cache invalidation behavior, rewrite behavior, and security headers.
日本語の概要は準備中です。原文の説明を表示しています。