Set a redesign direction for an existing website. Analyzes the user's intent, picks a palette and visual direction, and writes the target spec (PRODUCT.md, DESIGN.md, DESIGN.json) plus a reasoning trace at stardust/direction.md. Use when the user asks to redesign a site, refresh the design, set a new design direction, define a redesign target, or invokes /stardust:direct.
日本語の概要は準備中です。原文の説明を表示しています。
OCIOStateOfNebraska/stateofnebraska-aem☆ 32026年10月14日 更新
One-shot brand-faithful presales redesign of a website page. The user provides only the URL; everything else — extraction, tension identification, three differentiated variants (one fully cinematic), validation — is derived from the captured brand surface. Use when the user asks to "uplift", "refresh", or "redesign a site for presales" without wanting to coordinate the extract / direct / prototype chain themselves.
日本語の概要は準備中です。原文の説明を表示しています。
OCIOStateOfNebraska/stateofnebraska-aem☆ 32026年10月14日 更新
Elite frontend image-direction skill for generating premium, conversion-aware website design references. CRITICAL OUTPUT RULE — generate ONE separate horizontal image FOR EVERY section. A landing page with 8 sections produces 8 images. Never compress multiple sections into one image. Enforces composition variety (not always left-text / right-image), background-image freedom, varied CTAs, varied hero scales (giant / mid / mini minimalist), narrative concept spine, second-read moments, and a single consistent palette across all images. Optimized for landing pages, marketing sites, and product comps that developers or coding models can accurately recreate.
日本語の概要は準備中です。原文の説明を表示しています。
heyAyushh/stacc☆ 32026年9月21日 更新
Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards, generate fresh standalone images for sections or detail views instead of cropping old ones, avoid lazy under-generation, avoid cards-inside-cards-inside-cards UI, and keep the hero clean, spacious, readable, and visible on a small laptop.
日本語の概要は準備中です。原文の説明を表示しています。
heyAyushh/stacc☆ 32026年9月21日 更新
Flip a problem, goal, or decision 180 degrees to find what forward thinking misses. Asks what would guarantee failure, then works backward to what must be avoided or changed. Load when the user says "invert this", "flip this problem", "what would guarantee failure", "think backward", "reverse engineer the goal", "think about it backwards", or when deep-thinking diagnoses an inversion frame. Also triggers on "what's the opposite of success here", "how would we sabotage this". Two methods: Failure Inversion and Opposite Goal. Max 2 clarifying questions before inverting. Always returns forward actions. For broader analysis, deep-thinking calls this.
日本語の概要は準備中です。原文の説明を表示しています。
dvy1987/agent-loom☆ 32026年8月8日 更新
Nominates and assesses CRISPR off-target sites genome-wide. Enumerates candidate sites by mismatch and bulge tolerance with Cas-OFFinder/CRISPRitz, ranks them with the published CFD score (SpCas9-only, relative ranker) or MIT/CRISTA/energy models, runs variant-aware screening against gnomAD/individual genomes (CRISPRme), and frames the empirical genome-wide discovery assays (GUIDE-seq, CIRCLE-seq, CHANGE-seq, DISCOVER-seq, Digenome-seq) and high-fidelity nuclease choice (HiFi Cas9, Sniper-Cas9, eSpCas9, SpCas9-HF1). Use when assessing guide RNA specificity, choosing among candidate guides, screening a therapeutic guide against population variation, or planning empirical off-target validation. Distinguishes predicted vs detected vs validated. On-target activity scoring and deaminase (Cas-independent) base/prime-editor off-targets are separate skills.
日本語の概要は準備中です。原文の説明を表示しています。
peacezha/HPClaw☆ 32026年10月11日 更新
Annotate CLIP-seq peaks or crosslink sites to RNA features (5'UTR, CDS, 3'UTR, intron, splice junction, snoRNA, tRNA, ncRNA, repeat elements) with ChIPseeker, RCAS, RBP-Maps (Yeo splicing regulatory maps), and bedtools, applying feature-priority hierarchies, transcript-context resolution, and metagene aggregation. Use when characterizing where in transcripts an RBP binds, comparing peak distribution across regions, generating splicing-regulatory maps relative to alternative-splicing events, or distinguishing exonic vs intronic vs UTR binding.
日本語の概要は準備中です。原文の説明を表示しています。
peacezha/HPClaw☆ 32026年10月11日 更新
Detect single-nucleotide crosslink (CL) sites in CLIP-seq data using truncation patterns (iCLIP/eCLIP CITS), crosslink-induced mutations (HITS-CLIP CIMS deletions, PAR-CLIP T-to-C), or HMM/kernel-density methods (PureCLIP, PARalyzer, CTK). Use when single-nucleotide resolution is required for motif registration (mCross), allele-specific binding (BEAPR), variant-effect prediction, or comparing crosslink chemistry across CLIP variants.
日本語の概要は準備中です。原文の説明を表示しています。
peacezha/HPClaw☆ 32026年10月11日 更新
Call protein-RNA binding sites from CLIP-seq BAM with CLIPper, PureCLIP, Skipper, Piranha, omniCLIP, CTK, CLAM, or Paraclu. Use when choosing between coverage-based, HMM-based, beta-binomial window-based, and crosslink-site-based peak callers; applying ENCODE eCLIP thresholds (log2 IP/SMInput >= 3, -log10 p >= 3); deciding when SMInput is mandatory; or reconciling peak-set discordance between callers for the same RBP.
日本語の概要は準備中です。原文の説明を表示しています。
peacezha/HPClaw☆ 32026年10月11日 更新
Detect positive (diversifying / episodic / pervasive) selection using codon dN/dS frameworks. Implements PAML codeml site models (M0/M1a/M2a/M7/M8/M8a), branch models, branch-site model A (Zhang 2005), and HyPhy methods (BUSTED, BUSTED-S, BUSTED-MH, BUSTED-PH, MEME, FEL, FUBAR, aBSREL, SLAC, RELAX, GARD, FUBAR-MH). Includes McDonald-Kreitman framework (asymptotic alpha, impMKT, polyDFE, DFE-alpha, GRAPES) for within-species + divergence inference, RERconverge for trait-correlated rate shifts, CSUBST for convergent substitution, and PhyloAcc for accelerated noncoding evolution. Use when testing adaptive evolution at codons, branches, or full gene; running GARD recombination pre-screen; controlling alignment-error and gBGC false positives; reconciling PAML vs HyPhy results; or performing genome-scale selection scans.
日本語の概要は準備中です。原文の説明を表示しています。
peacezha/HPClaw☆ 32026年10月11日 更新
Use this skill when the user asks about FMCSA investigation types — Focused Investigation vs Comprehensive Review vs Compliance Review (CR) vs Investigation, when each is triggered, scope differences, on-site vs off-site, and how to prepare for each. Cite 49 CFR 385 Subpart C + D.
日本語の概要は準備中です。原文の説明を表示しています。
x3allamerican/skills☆ 32026年5月17日 更新
Use this skill when FMCSA conducts an off-site investigation (less formal than CR). Covers the document-request approach and how to respond efficiently.
日本語の概要は準備中です。原文の説明を表示しています。
x3allamerican/skills☆ 32026年5月17日 更新
Adversarial reviewer for The Federated Harbor whitepaper — the third paper in the Curiositech sequence after Anchor and Bonded Commons. Probes federation-specific threats: trust transitivity, cross-harbor token forgery, federated revocation under partition, cross-harbor Sybil, cross-domain settlement, equivocation, bond-pool draining, cold-start joining, federation-operator Sybil. Use during a versioned red-vs-white round; pairs with federated-harbor-whitehat. NOT for incident response, NOT for the Anchor or Bonded papers (use redteam-review).
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 32026年10月15日 更新
Drafting and iterating sections of The Federated Harbor whitepaper — the third paper in the Curiositech sequence after Anchor (local identity) and Bonded Commons (local coordination), extending coordination across machines and administrative domains. Use when authoring a section, rewriting a section after a redteam/whitehat round, or composing a new chapter. NOT for marketing copy, NOT for the other two papers, NOT for production threat response.
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 32026年10月15日 更新
Schema design, normalization decisions, indexing strategies, and migration safety for relational databases. Use when designing tables, choosing between normalize vs denormalize, selecting index types, planning zero-downtime migrations, or setting up connection pooling. Activate on "schema design", "normalization", "denormalization", "foreign key", "index strategy", "migration", "connection pooling", "composite key", "surrogate key", "soft delete", "polymorphic association". NOT for PostgreSQL-specific query tuning or EXPLAIN analysis (use postgresql-optimization), NoSQL or document database design, or cloud database provisioning.
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 32026年10月15日 更新
Expert in developer tool documentation as a product. Activate on: docs site, getting started guide, API reference, developer documentation, Docusaurus, Mintlify, Nextra, ReadMe, migration guide, troubleshooting page, docs information architecture, documentation testing, llms.txt. NOT for: marketing copy (use seo-content-blogging), API design itself (use api-architect), general technical writing (use technical-writer).
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 32026年10月15日 更新
Debugs recorded DAG lineage through historical inspection, deterministic decision replay when prerequisites hold, and clearly labeled counterfactual or live re-execution. Activate on "debug DAG", "replay execution", "inspect node state", "compare runs", or "execution diff". NOT for live monitoring (use dag-runtime + websocket-streaming), failure analysis (use dag-ops), or general code debugging.
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 32026年10月15日 更新
Professional CV and resume builder transforming career narratives into ATS-optimized, multi-format resumes. Integrates with career-biographer for data and competitive-cartographer for positioning. Generates PDF, DOCX, LaTeX, JSON Resume, HTML, and Markdown. Activate on 'resume', 'CV', 'ATS optimization', 'job application'. NOT for cover letters, portfolio websites (use web-design-expert), LinkedIn optimization, or interview preparation.
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 32026年10月15日 更新
Collage as a web design aesthetic — overlapping elements, mixed media, cut-out shapes, scrapbook layouts, and editorial magazine spreads adapted for the web. CSS techniques for layered compositions using z-index stacking, clip-path, mix-blend-mode, parallax layering, and grid-breaking layouts. Activate on 'collage web', 'editorial layout', 'magazine layout', 'overlapping elements', 'scrapbook', 'cut-out aesthetic', 'mixed media web', 'layered composition', 'grid-breaking', 'editorial web design', 'fashion website layout', 'David Carson'. NOT for photo collage/gallery grids (use collage-layout-expert), maximalist density (use maximalist-web-design), neobrutalism (use neobrutalist-web-designer).
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 32026年10月15日 更新
Runs an iterative, conversational product-discovery process with a founder/stakeholder: structured interview, live low-fi wireframing, a linked feature/page node-graph built up as you go, a founder-confirmed lock-in checkpoint, then a generated PRD, a Mermaid-rendered sitemap, and a mockup with a full design system (palette, typography, dark mode). Use when building or operating an AI product-discovery chatbot, or when running founder/stakeholder discovery by hand and you need the structure (interview script, node-graph schema, PRD template, design-system handoff order). NOT for implementing the spec'd product once locked — hand off to feature-specific skills (ideal-web-app-builder, tailwind-v4-expert, color-theory-palette-harmony-expert, typography-expert, dark-mode-design-expert) for that. NOT for one-shot PRD generation without an interview loop — if the founder already has a written spec, this process is unnecessary overhead.
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 32026年10月15日 更新
Use when designing or fixing a Content Security Policy on a real site, choosing between nonce-based and hash-based CSP, adding strict-dynamic, debugging "Refused to execute inline script" errors, deploying CSP in report-only mode first, configuring report-to / report-uri, or auditing an existing policy for unsafe-inline / unsafe-eval / wildcards. Triggers: "CSP blocks legitimate inline script", strict-dynamic, nonce-{RANDOM}, sha256-{HASH}, object-src none, base-uri none, frame-ancestors, Trusted Types, X-Content-Security-Policy obsolete, report-only vs enforced. NOT for general HTTP security headers (HSTS, COOP/COEP), Trusted Types deep dive, CORS configuration, or building a WAF.
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 32026年10月15日 更新
Own whether a multi-document product-architecture binder is internally consistent, complete against its stated customer/contingency/architecture coverage, and honest about which older product ambitions it has absorbed, superseded, deferred, contradicted, orphaned, or rejected. Use when running a binder Architect of Record pass, before an implementation chain cites a binder chapter as ready, when a proof-gate owner is missing, or when reconciling the binder against the older ambition corpus (website, plans, examples, ADRs). NOT for auditing a single Claude Skill bundle's structure or frontmatter (use skill-hygiene), rendering a single-PM accept/reject verdict on one finished deliverable (use port-daddy-user-surrogate-pm-review), or sequencing/stewarding a roadmap's sidequests once a gap or operator decision has been surfaced (use legible-roadmap-with-sidequests).
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 32026年10月15日 更新
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.
日本語の概要は準備中です。原文の説明を表示しています。
balsm-health/website☆ 32026年10月12日 更新
Google SEO APIs: Search Console (Search Analytics, URL Inspection, Sitemaps), PageSpeed Insights v5, CrUX field data with 25-week history, Indexing API v3, and GA4 organic traffic. Provides real Google field data for Core Web Vitals, indexation status, search performance, and organic traffic trends. Use when user says "search console", "GSC", "PageSpeed", "CrUX", "field data", "indexing API", "GA4 organic", "URL inspection", or "real CWV data".
日本語の概要は準備中です。原文の説明を表示しています。
balsm-health/website☆ 32026年10月12日 更新