ideate
무료Orchestrate ideation from raw input to validated ideation outputs with shard composition
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
1.5천건 · 관련도순
Orchestrate ideation from raw input to validated ideation outputs with shard composition
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Decompose approved architecture design into IA shards and layered spec structure, then validate dependencies and tracking outputs
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Senior Kotlin specialist code review — framework-agnostic. Use whenever the user asks to review, audit, critique, or get feedback on Kotlin code, a file, a class, a function, a module, a diff, a branch, a commit, or a pull request. Judges Kotlin language idioms, logic correctness, architecture and layering, concurrency (coroutines, Flow, structured concurrency, cancellation, race conditions), null safety, exception safety, testability, performance, and security. Detects force-unwraps, unchecked casts, GlobalScope, leaked mutability, broken structured concurrency, hidden side effects, weak abstractions, untestable seams, allocation hot spots, weak crypto, input-validation gaps, and PII logging. Outputs prioritized findings with file:line anchors and minimal-diff fixes. No assumptions about DI framework, UI framework, or build system.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematic writing framework for philosophy and interdisciplinary academic papers from optimized outline to submission-ready manuscript. Use when users want to: (1) write a paper from a detailed outline, (2) ensure quality control during writing, (3) maintain consistency across chapters, (4) prepare a submission-ready manuscript, or (5) systematically execute a planned paper. Triggered by phrases like 'write the paper from this outline,' 'compose the full manuscript,' 'execute the outline,' or when users have completed strategic planning (academic-paper-strategist skill) and are ready to write. Takes optimized outline as input; outputs complete manuscript with iterative quality checks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build high-quality MCP servers with strong tool design, structured outputs, clear error handling, and realistic evaluations. Use when creating or improving MCP servers in TypeScript or Python for external APIs, services, or internal platforms.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when building applications with Gemini API hosted models, including Gemini and Gemma 4, working with multimodal content (text, images, audio, video), implementing function calling, using structured outputs, or needing current model specifications. Covers SDK usage (google-genai for Python, @google/genai for JavaScript/TypeScript, com.google.genai:google-genai for Java, google.golang.org/genai for Go), model selection, and API capabilities.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate GCI competition predictions and notebook outputs against expected schema, metric, and submission constraints.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create and render fixed-canvas editable visual designs, including posters, marketing graphics, covers, menus, banners, and social cards. Default outputs include fixed and editable HTML, PNG, a mouse editor with scan and exploded layer views, and an evidence-backed Design Replay. Do not use for websites, slide decks, videos, or standalone logo systems. Always use this skill when the project contains `poster.json`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Convert any document into a production-ready Ozor.ai video prompt. Use this skill whenever the user uploads a document (PDF, PowerPoint, Google Doc, Markdown, text file, or URL) and wants to turn it into a video. Also trigger when the user mentions 'turn this doc into a video', 'make a video from this PDF', 'video from my pitch deck', 'convert this presentation to video', 'video from this blog post', 'video from these release notes', 'create a video from this document', 'turn this into an explainer', or any request to transform written content into video format using Ozor. This skill reads the document, extracts the core message, structures it into scenes, and outputs a complete prompt the user can paste directly into Ozor.ai.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Define, validate, run, resume, and audit repo-local multi-step automations with current `asc workflow` and `.asc/workflow.json`, including step outputs and safe release/TestFlight workflows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Choose OpenRouter models and routers, query live catalog data, use structured outputs and batch inference, and debug routing with metadata. Use when working with OpenRouter APIs, openrouter/auto, openrouter/free, model discovery, pricing, providers, batch jobs, or structured JSON responses.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for training outputs, metrics logging, logtree reports, tracing/profiling, and debugging training runs. Use when the user asks about training logs, metrics, debugging, tracing, profiling, timing, Gantt charts, or understanding training output files.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Senior engineering analyst for code review, plan review, and automation review. Use when: (1) "review this", "analyze the code", "check this plan", (2) After implementation to verify quality, (3) "is this good enough?", (4) Before marking a task complete, (5) Reviewing a blueprint from /architect, (6) Reviewing output from /refinery. Four-lens review: architecture, code quality, reliability, performance. Reads from system/blueprints/ and source code. Outputs to system/reviews/.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Productivity analyst that maps your workflow, scores tasks, and builds a prioritized automation plan. Use when: (1) "audit my workflow", "what should I automate?", "productivity review", (2) Starting a new project and need to identify high-leverage tasks, (3) Feeling overwhelmed and need to prioritize, (4) After /compounder surfaces new friction or patterns. Reads compounder insights when available. Outputs to system/audit-report.md.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Weekly review partner that compounds productivity gains over time. Tracks velocity, logs friction, sets next-week targets, recognizes patterns across weeks, and feeds insights back to the audit for the next loop. Use when you want a weekly review, need to identify friction, want to see patterns, or want to update your system map. Part of the architect-system loop. Outputs to system/compounder/week-{date}.md.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Convergence loop that iteratively improves work until quality thresholds are met. Scores, diagnoses specific weaknesses, rewrites, re-scores, and repeats until all dimensions reach 8/10 or diminishing returns are detected. Use when you want to refine or iterate on work, after the analyst gives a REVISE verdict, or when output quality is below your bar. Part of the architect-system loop. Outputs to system/refinery-log.md.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Senior engineering analyst for code review, plan review, and automation review. Four-lens review covering architecture, code quality, reliability, and performance, each scored 1-10. Delivers APPROVE, REVISE, or REJECT verdicts. Use when you need a code review, plan review, quality check, or want to verify work before shipping. Part of the architect-system loop. Reads from system/blueprints/ and source code. Outputs to system/reviews/.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Productivity analyst that maps your workflow, scores tasks by time cost and energy drain, and builds a prioritized 4-week automation plan. Use when you want to audit your workflow, figure out what to automate, do a productivity review, identify high-leverage tasks, feel overwhelmed and need to prioritize, or after the compounder surfaces new friction. Part of the architect-system loop. Outputs to system/audit-report.md.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Weekly review partner that compounds productivity gains over time. Use when: (1) "weekly review", "what did I accomplish this week?", "compound my gains", (2) End of work week to review progress, (3) "what patterns are emerging?", (4) "update the system map", (5) Feeling stuck and need to identify friction. Reads all system/ files to synthesize progress. Outputs to system/compounder/week-{date}.md. Feeds insights back to /audit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Convergence loop that iteratively improves work until quality thresholds are met. Use when: (1) "refine this", "make this better", "iterate on this", (2) After /analyst gives a REVISE verdict, (3) Output quality is below 8/10, (4) "run the refinery loop on this". Reads analyst reviews from system/reviews/. Generates, scores, diagnoses, rewrites, re-scores. Stops when all dimensions >= 8/10 or diminishing returns detected. Outputs to system/refinery-log.md.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Solution architect that creates implementation blueprints before building. Use when: (1) "architect this", "design a solution", "blueprint for", (2) Taking a task from the audit report and need an implementation plan, (3) "how should I build this?", "plan before building", (4) Before any non-trivial implementation. Reads from system/audit-report.md. Outputs to system/blueprints/.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Solution architect that creates implementation blueprints before building. Maps 2-3 approaches ranked by simplicity, creates phased build plans with rollback points, and checks dependencies. Use when you need to design a solution, create a blueprint, plan before building, or take a task from the audit and need an implementation plan. Part of the architect-system loop. Reads from system/audit-report.md. Outputs to system/blueprints/.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks to "implement LLM-as-judge", "compare model outputs", "create evaluation rubrics", "mitigate evaluation bias", or mentions direct scoring, pairwise comparison, position bias, evaluation pipelines, or automated quality assessment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
You are an AI product engineer who has shipped LLM features to millions of users. You've debugged hallucinations at 3am, optimized prompts to reduce costs by 80%, and built safety systems that caught thousands of harmful outputs. You know that demos are easy and production is hard.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.