Source control and artifact exposure (.git, .svn, .hg, backups, .env). Use when recon finds VCS paths, 403 on hidden dirs, or backup/config leaks during authorized testing.
日本語の概要は準備中です。原文の説明を表示しています。
911 件 ・ 関連度順
概要と使いどころ
Source control and artifact exposure (.git, .svn, .hg, backups, .env). Use when recon finds VCS paths, 403 on hidden dirs, or backup/config leaks during authorized testing.
日本語の概要は準備中です。原文の説明を表示しています。
Hash attack playbook. Use when exploiting length extension, MD5/SHA1 collisions, HMAC timing leaks, birthday attacks, or hash-based proof of work in CTF and authorized testing scenarios.
日本語の概要は準備中です。原文の説明を表示しています。
Design habit-forming product loops using the Hook Model (Trigger, Action, Variable Reward, Investment). Use when the user mentions "users arent coming back", "habit formation", "engagement loops", "habit zone", or "the manipulation matrix". Also trigger when designing notification or re-engagement strategies, building streaks or progress systems, or analyzing why users stop after signup. Covers ethics evaluation and onboarding for habits. For friction reduction and B=MAP, see improve-retention. For viral sharing, see contagious.
日本語の概要は準備中です。原文の説明を表示しています。
Guided journey from a live website that underperforms to a prioritized, evidence-backed backlog of conversion, usability, message, and speed fixes - each shipped as a testable experiment. Orchestrates eight skills phase by phase - cro-methodology, ux-heuristics, refactoring-ui, web-typography, storybrand-messaging, high-perf-browser, made-to-stick, design-everyday-things - asking the user questions at every decision point and recording results in the project docs/ folder (WEBSITE.md, DESIGN.md, IMPROVE-WEBSITE-PLAN.md) so the journey resumes across sessions. Use when the user wants to fix a landing page that isn't converting, diagnose why visitors leave, audit for clarity and usability, or says 'the homepage feels off but a redesign didn't help'. No site yet, create-website; converts but needs traffic, grow-website; if the friction is in a product app, not the marketing site, improve-app; if one specific flow leaks, conversion-optimization. For one framework in isolation, invoke that skill directly.
日本語の概要は準備中です。原文の説明を表示しています。
Decides how the business is financed and what that financing then requires of it — debt versus equity, weighted average cost of capital as a hurdle rate, how much leverage cash flow can carry, and the financial, affirmative and negative covenants, definitions, test dates and cure rights that come attached. Use this to evaluate a financing option, set an investment hurdle, check whether a planned decision will trip a covenant, or work out what a lender can do when one breaks.
日本語の概要は準備中です。原文の説明を表示しています。
Builds and stress-tests financial models for forecasting, scenario planning, and decision support — revenue build, cost structure, driver logic, and the sensitivities that show where a plan breaks. Use this to model a decision's financial consequence, build a forecast or long-range plan, evaluate an investment or hire, or pressure-test someone else's model before relying on it.
日本語の概要は準備中です。原文の説明を表示しています。
Baidu Web Search skill for real-time Chinese web information retrieval. Breaks through static knowledge base limitations to get the latest news and information. Use when user needs to search the Chinese web for current information.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive security and correctness audit of a branch's changes. Use for thermo nuclear, thermonuclear, or deep review requests, or branch/PR diff audits focused on bugs, breaking changes, security issues, devex regressions, and feature-gate leaks.
日本語の概要は準備中です。原文の説明を表示しています。
NGS analysis toolkit. Used for BAM to bigWig conversion, quality control (correlation, PCA, fingerprint plots), heatmaps/feature plots (TSS, peaks), suitable for ChIP-seq, RNA-seq, ATAC-seq visualization.
日本語の概要は準備中です。原文の説明を表示しています。
Detect pauses and silence in audio using local dynamic thresholds. Use when you need to find natural pauses in lectures, board-writing silences, or breaks between sections. Uses local context comparison to avoid false positives from volume variation.
日本語の概要は準備中です。原文の説明を表示しています。
Optimize Python code for reduced memory usage and improved memory efficiency. Use when asked to reduce memory footprint, fix memory leaks, optimize data structures for memory, handle large datasets efficiently, or diagnose memory issues. Covers object sizing, generator patterns, efficient data structures, and memory profiling strategies.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze and resolve BGP oscillation and BGP route leaks in Azure Virtual WAN–style hub-and-spoke topologies (and similar cloud-managed BGP environments). Detect preference cycles, identify valley-free violations, and propose allowed policy-level mitigations while rejecting prohibited fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Turns product or tech specs into concrete Notion tasks that Claude code can implement. Breaks down spec pages into detailed implementation plans with clear tasks, acceptance criteria, and progress tracking to guide development from requirements to completion.
日本語の概要は準備中です。原文の説明を表示しています。
Expert Kubernetes architect specializing in cloud-native infrastructure, advanced GitOps workflows (ArgoCD/Flux), and enterprise container orchestration. Masters EKS/AKS/GKE, service mesh (Istio/Linkerd), progressive delivery, multi-tenancy, and platform engineering. Handles security, observability, cost optimization, and developer experience. Use PROACTIVELY for K8s architecture, GitOps implementation, or cloud-native platform design.
日本語の概要は準備中です。原文の説明を表示しています。
Provides React Native performance optimization guidelines for FPS, TTI, bundle size, memory leaks, re-renders, and animations. Applies to tasks involving Hermes optimization, JS thread blocking, bridge overhead, FlashList, native modules, or debugging jank and frame drops.
日本語の概要は準備中です。原文の説明を表示しています。
Before and after changing anything shared — a function's return value, a signature, a schema, a label set, a config default, a constant, a file format — find every consumer and actually run them. Catches the change that looks purely additive but silently breaks a contract in a file you never opened. Use when editing shared code, adding a field/column/return element, renaming, changing units or defaults, or touching a pipeline that produces reported numbers.
日本語の概要は準備中です。原文の説明を表示しています。
Writing a Succession-style ensemble series (继承之战群像剧写法) — distilled from Jesse Armstrong's complete shooting scripts for all four seasons, 39 episodes (Faber 2023), with his introductions and footnotes, plus Frank Rich's and Lucy Prebble's essays on the writers' room. Covers the invisible-act three-test for scripts with no ACT marks, container episodes built on a ceremony's running order, pressure chambers, one core question per episode, finales with fewer and longer scenes, the absent protagonist at the climax, humiliation passed downward, stage directions carrying subtext and "maybe", reversals turned on one word, writing long, alts, the mega-chart, and engineering an ending once the plot engine loses pressure. Use when the user wants a dynastic family drama, a media-power ensemble, a wedding/funeral/summit set piece, a streaming hour with no act breaks, a finale that redraws alliances, or asks how to "Succession-ize" a script or kill a lead mid-season.
日本語の概要は準備中です。原文の説明を表示しています。
Worked qupai-system (曲牌体) opera scripts, act by act. Guan Hanqing's three surviving zaju (窦娥冤/救风尘/金线池 — twelve acts, 126 tunes, one mode and one rhyme per act, sung/spoken ratios); Tang Xianzu's 牡丹亭 (55 scenes, ~420 tunes, 集唐 closing quatrains, the 圆驾 south-north composite suite); Kong Shangren's 桃花扇 (44 scenes plus four unnumbered, the 副末 frame line, upper/lower halves, a fan's seven transformations, his sixteen 凡例); 长生殿 (Wang Jilie's fifty-scene staging table); Wei Minglun's 巴山秀才 (1983 Sichuan 高腔, 43 tunes, nine 帮腔 passages). Every case states its edition and collation status, then structure, tunes, stage conventions and transferable devices. Method is in sw-chinese-opera-qupai; this skill holds the worked scripts. Use when you want a real example of how a 传奇 or 杂剧 is assembled, need actual scene counts and tune counts to imitate, are judging where a famous script breaks prosody, or need models for 副末开场, 集唐下场诗, 南北合套 or 帮腔 (曲牌体全本/牡丹亭/桃花扇/窦娥冤/救风尘/长生殿/巴山秀才/唱段表/结构表).
日本語の概要は準備中です。原文の説明を表示しています。
Writing screenplays in the style of Ozu Yasujiro and Noda Kogo (小津安二郎・野田高梧) — distilled from six complete screenplays (晚春 Late Spring, 麦秋 Early Summer, 东京物语 Tokyo Story, 浮草 Floating Weeds, 秋日和 Late Autumn, 秋刀鱼之味 An Autumn Afternoon). Covers the "family member leaves" master plot, off-screen events / on-screen reactions, lie-driven plots, minimal-syllable confessions, go-between characters, faceless suitors, pillow-shot scene breaks, echoing objects, mirror characters, children's subplots as metaphor, displaced quarrels, the single-monologue rule, diminishing endings, Ozu's script format and stage-direction vocabulary. Use when the user wants to write a quiet family drama, a 小津风 / 侘寂 / 日常系 script, a story about marrying off a daughter, aging parents, or wants dialogue that says less and means more.
日本語の概要は準備中です。原文の説明を表示しています。
Draw cloud architecture diagrams for AWS, Azure or GCP with the official provider icon sets, using TerraVision. Use whenever the user asks to draw, diagram, sketch or visualize a system on AWS, Azure or Google Cloud, or one built from their services (Lambda, DynamoDB, S3, EC2, EKS, RDS, API Gateway, Azure Functions, App Service, AKS, Cosmos DB, Cloud Run, GKE, BigQuery and the like), even if they never say 'cloud', 'diagram' or a tool name; also for a diagram of Terraform code. Prefer it over Mermaid, PlantUML, hand-written SVG or ASCII, which cannot use the official icons or VPC/subnet grouping. Not for diagrams that are not cloud infrastructure: sequence diagrams, flowcharts, class or ER diagrams, code or module structure, org charts, on-premises-only networks; use Mermaid or similar for those. Works with or without Terraform: with Terraform code the diagram comes from terraform plan; without it, write a small JSON graph and render it.
日本語の概要は準備中です。原文の説明を表示しています。
Use whenever a build emits or repairs .agentlas/routing-card.json — the shared card contract for the single-agent builder, the team builder, and the packager. States what belongs in every field, which fields the hub can actually match on, and which fields silently break matching when a sentence leaks into them.
日本語の概要は準備中です。原文の説明を表示しています。
Builds an Azure portal deep link to a specific blade/menu item for supported Microsoft.ContainerService, Microsoft.Kubernetes, and Microsoft.Compute resources using the aks-search-direct-mid semantic search API. WHEN: 'find where in the Azure portal to do something', 'search the portal for an operation', 'construct a portal link from a search query and a resource'.
日本語の概要は準備中です。原文の説明を表示しています。
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
日本語の概要は準備中です。原文の説明を表示しています。
Breaks down complex software, writing, or research tasks into small, atomic, independently completable units with dependency graphs and milestone breakdowns. Use when the user asks to plan a project, decompose a feature, create subtasks, split up work, or needs help organizing a large piece of work into a step-by-step plan. Triggered by phrases like "break down", "decompose", "where do I start", "too big", "split into tasks", "work breakdown", or "task list".
日本語の概要は準備中です。原文の説明を表示しています。