Build investor-ready pitch scripts in multiple formats (10-min, 5-min, 2-min, 1-min elevator, investor email). Produces pitch narratives, Q&A preparation, pitch scoring rubric, and optional investor roleplay practice. Use when the user wants to create a pitch, prepare for investor meetings, craft a startup pitch, write a fundraising narrative, or practice their pitch. Triggers for "pitch deck", "investor pitch", "pitch my startup", "fundraising deck", "seed deck", "how to pitch", "investor meeting", "demo day", "prepare pitch", "pitch script", "elevator pitch for investors", "pitch practice", "practice my pitch", "investor roleplay", or any request to present a startup to investors, accelerators, or partners. Works standalone — no prior startup-design session needed, but leverages its output if available.
日本語の概要は準備中です。原文の説明を表示しています。
sathishssj3/Stereix-Engine☆ 22026年10月4日 更新
How to write modern Swift well — modeling with value types, Swift 6 data-race safety and approachable concurrency (@concurrent, main-actor-by-default, actors, task groups), protocols and generics (some vs any), API design, performance and ARC, Swift Testing, macros, and the modern language features agents don't know about yet. Use when writing, reviewing, or migrating Swift, or when a concurrency error, a hang, a data race, a retain cycle, or a performance problem needs fixing.
日本語の概要は準備中です。原文の説明を表示しています。
sathishssj3/Stereix-Engine☆ 22026年10月4日 更新
Raw mechanical interfaces fusing Swiss typographic print with military terminal aesthetics. Rigid grids, extreme type scale contrast, utilitarian color, analog degradation effects. For data-heavy dashboards, portfolios, or editorial sites that need to feel like declassified blueprints.
日本語の概要は準備中です。原文の説明を表示しています。
sathishssj3/Stereix-Engine☆ 22026年10月4日 更新
The original v1 taste-skill, preserved for projects depending on its exact behavior. The current default is `design-taste-frontend` (v2 experimental), which is a substantial rewrite. Use this v1 install name only if you need exact backward compatibility.
日本語の概要は準備中です。原文の説明を表示しています。
sathishssj3/Stereix-Engine☆ 22026年10月4日 更新
Standardizes development environment setup across machines by generating tool version configs (Node, Python, Ruby), package manager configs (pnpm, Volta, asdf, mise), environment variable templates, and setup scripts with onboarding documentation. Use when users need to "setup dev environment", "standardize tooling", "configure version managers", or "create onboarding scripts".
日本語の概要は準備中です。原文の説明を表示しています。
sathishssj3/Stereix-Engine☆ 22026年10月4日 更新
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.
日本語の概要は準備中です。原文の説明を表示しています。
sathishssj3/Stereix-Engine☆ 22026年10月4日 更新
Estimates infrastructure needs based on traffic forecasts, workload analysis, and performance requirements with sizing recommendations and cost trade-offs. Use for "capacity planning", "infrastructure sizing", "resource estimation", or "scalability planning".
日本語の概要は準備中です。原文の説明を表示しています。
sathishssj3/Stereix-Engine☆ 22026年10月4日 更新
Use when designing a Spark feature or writing or materially revising a design proposal that needs repository-first research, user input on unresolved key choices, and an owner-aligned implementation plan before code changes.
日本語の概要は準備中です。原文の説明を表示しています。
zendev-lab/spark☆ 22026年10月19日 更新
Use when a running Spark or DSH web service needs real-browser verification — page load, client-plugin boot errors, console errors, failed requests, or onboarding/dialog rendering — with the repository's own Playwright chromium.
日本語の概要は準備中です。原文の説明を表示しています。
zendev-lab/spark☆ 22026年10月19日 更新
Use when a Spark branch or pull request needs final diff hygiene, validation selection, commit scope, remote topology, and readiness checked before publication.
日本語の概要は準備中です。原文の説明を表示しています。
zendev-lab/spark☆ 22026年10月19日 更新
Use when a Spark change needs its authoritative owner, affected boundaries, risks, acceptance criteria, and smallest verifiable slice established before implementation or review.
日本語の概要は準備中です。原文の説明を表示しています。
zendev-lab/spark☆ 22026年10月19日 更新
Use when a Spark implementation needs an evidence-based review for correctness, ownership, compatibility, failure handling, maintainability, and unnecessary complexity.
日本語の概要は準備中です。原文の説明を表示しています。
zendev-lab/spark☆ 22026年10月19日 更新
Use when a research note system needs architecture, when MOCs, frontmatter standards, and retrieval patterns must be designed for years of work, or when an existing vault has outgrown its structure and must migrate without breaking years of links.
日本語の概要は準備中です。原文の説明を表示しています。
OnourImpram/claude-code-for-social-scientists☆ 22026年9月6日 更新
Use before sensitive, clinical, identifying, or raw interview data is placed in front of an AI tool, when transcripts or student materials need de-identification, or when a data-minimization gate must run before any analysis or drafting.
日本語の概要は準備中です。原文の説明を表示しています。
OnourImpram/claude-code-for-social-scientists☆ 22026年9月6日 更新
Use when a systematic, scoping, or rapid review needs a reproducible pipeline: protocol framing (PICO/SPIDER/PCC), a logged search string, title/abstract and full-text screening with recorded exclusion reasons, and PRISMA flow counts, with the human as the deciding screener.
日本語の概要は準備中です。原文の説明を表示しています。
OnourImpram/claude-code-for-social-scientists☆ 22026年9月6日 更新
Use when a Claude Code session loops, drifts from scope, claims a fix that CI rejects, hits context, PATH, or permission walls, or fails in a way another retry will not solve and a root cause diagnosis is needed instead.
日本語の概要は準備中です。原文の説明を表示しています。
OnourImpram/claude-code-for-social-scientists☆ 22026年9月6日 更新
Use when designing a course, assessment, or student-feedback workflow and deciding where AI assistance is acceptable, when grading or feedback must stay within academic-integrity and FERPA/KVKK boundaries, or when AI-use rules for students need stating.
日本語の概要は準備中です。原文の説明を表示しています。
OnourImpram/claude-code-for-social-scientists☆ 22026年9月6日 更新
Use when a study needs a preregistration or a frozen analysis plan, when confirmatory and exploratory analyses must be separated, or when every deviation from the registered plan must be logged before the result is reported.
日本語の概要は準備中です。原文の説明を表示しています。
OnourImpram/claude-code-for-social-scientists☆ 22026年9月6日 更新
Use when a draft in Turkish, English, or both reads as AI-generated and needs revision that removes machine writing patterns and translation calques while preserving meaning, citations, statistics, and the author's voice.
日本語の概要は準備中です。原文の説明を表示しています。
OnourImpram/claude-code-for-social-scientists☆ 22026年9月6日 更新
Use when an ethics committee or IRB application involves AI anywhere in the pipeline, when KVKK, GDPR, or EU AI Act duties must be mapped to a study, or when consent and disclosure language about AI use needs drafting before submission.
日本語の概要は準備中です。原文の説明を表示しています。
OnourImpram/claude-code-for-social-scientists☆ 22026年9月6日 更新
Use when authorship order, CRediT contribution roles, or AI-assistance attribution must be recorded transparently for a manuscript, when an author dispute needs an evidence trail, or before a contributorship statement is required at submission; this skill maintains the human-attribution ledger of who contributed what and in which role (authorship order, CRediT taxonomy, revision responsibilities), which is distinct from the disclosure-metadata audit owned by ai-disclosure-auditor.
日本語の概要は準備中です。原文の説明を表示しています。
OnourImpram/claude-code-for-social-scientists☆ 22026年9月6日 更新
Use when a study's materials, data, code, or preprint need an open-science release: license choice, a persistent DOI (Zenodo/OSF), README and metadata, and an access-and-embargo decision that respects ethics constraints.
日本語の概要は準備中です。原文の説明を表示しています。
OnourImpram/claude-code-for-social-scientists☆ 22026年9月6日 更新
Use when choosing a journal for a finished or nearly finished manuscript, when index status in Scopus, SSCI, ESCI, or TR Dizin must be confirmed, when a venue looks predatory, or when a cover letter needs drafting from the manuscript's actual claims.
日本語の概要は準備中です。原文の説明を表示しています。
OnourImpram/claude-code-for-social-scientists☆ 22026年9月6日 更新
Use when building slides, a poster, or a lightning talk from a manuscript, when a presentation must exist in Turkish and English, or when conference visuals need a traceability check so every number on a slide matches the analysis behind it.
日本語の概要は準備中です。原文の説明を表示しています。
OnourImpram/claude-code-for-social-scientists☆ 22026年9月6日 更新