'ideas' 검색 결과

Generate ideas via named methods from creative practice.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Resolución estructurada de problemas en 6 pasos: Definición del problema, objetivos, lluvia de ideas, evaluación, implementación y revisión.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Given the product and the existing page inventory, identify missing blog topics and generate new blog posts that capture search/AI intent using the query-fanout pattern. Use this skill whenever the user asks to "spawn blogs", "generate blog posts", "expand the blog", "build out a content cluster", "write blog ideas", "cover more search intents", "query fanout for blogs", or wants new long-form content that supports existing pillars. Output is one new post per topic in the project's existing post format (markdown, MDX, component, or CMS migration note), with frontmatter shape mirrored from an existing post.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says 'co-marketing,' 'partner marketing,' 'joint campaign,' 'who should we partner with,' 'integration marketing,' 'cross-promotion,' 'collaborate with another company,' 'partnership ideas,' or 'co-brand.' For customer referral programs, see referrals. For launch-specific partnerships, see launch.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use before creative or constructive work (features, architecture, behavior). Transforms vague ideas into validated designs through disciplined reasoning and collaboration.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Produce titles, thumbnails, description, chapters, and metadata. Use at the package stage or any time after gate 1, or when the user says "title ideas", "thumbnail", or "package this".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Distill an already-built or near-launch product into one incisive brand kernel — the "reveal" already hiding in its name, story, or the product itself — then build the name, voice, visual identity, and a developer-ready handoff kit around it. This is LATE-STAGE branding: use it when there is a real, thought-through product that is about to launch, or already live but not explained in a way people grasp in an instant. Use whenever the user wants to name or rename a product, find a tagline or slogan, create a brand identity / brand kit / style guide / design system, design a logo, wordmark, palette, or type system, mock up a homepage for a launch, or hand brand assets to a coding agent (Claude Code, Codex, Cursor). Trigger even when the user only says their product needs to "land" or "feel like" something, or that they can't explain it simply yet. Do NOT use for half-baked, pre-product ideas with nothing to excavate — this skill extracts a kernel that already exists; it does not invent one from a blank canvas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

사용자가 HWP나 HWPX 양식 파일을 주면서 "이 양식으로 앱을 만들어 달라", "양식을 전산화하자", "이 서식에 입력하고 출력하고 통계 내는 웹앱"이라고 할 때 사용한다. 양식의 칸을 그대로 데이터베이스로 옮기지 않고, 칸을 분류해 이용자 명부와 연결하고, 판정을 거쳐 앱과 HWP 출력을 만드는 절차다. 사회복지 기관의 일지, 명단, 대장, 보고서 서식에 쓴다. Use when a Korean social-welfare practitioner hands over an HWP/HWPX form and wants an app built from it. For app ideas without a form file, use welfare-app-assess instead.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use before creative or constructive work (features, architecture, behavior). Transforms vague ideas into validated designs through disciplined reasoning and collaboration.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Exhaustive idea extraction through recursive breadth-before-depth exploration with Deep Think protocol and fractal structure. Use during /ideate to transform raw ideas into comprehensive, structured ideation output. Writes to a fractal folder hierarchy — every node has an index, CX file, and children.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build and run the owner's self-branding system in a structured way across LinkedIn, Substack, dev.to, X, profile rewrites, recurring series, and comment strategy. Use when the owner asks for positioning, a branding plan, profile updates, content drafts, a publishing sequence, comment ideas, or help maintaining a consistent public voice. Optimize for operator credibility: specific experience, defensible numbers, concrete artifacts, and category ownership.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Autonomously improve a real artifact (code, training recipe, agent harness, data pipeline, prompt) against an objective and an evaluator, using Hypothesis Tree Refinement (HTR) from the Arbor paper. Use this whenever someone wants to iteratively optimize something over many experiments without overfitting — e.g. "get my model's eval score up", "improve this agent/harness", "tune this pipeline", "beat the baseline on this benchmark", "run a search over approaches and keep the best", "do an MLE-bench / Kaggle-style optimization", or any long-horizon "make this artifact better and don't just memorize the dev set" task. Trigger it even when the user doesn't say "Arbor" or "hypothesis tree" but describes repeated experiment-and-evaluate loops, branching exploration of competing ideas, or worries about a dev/test gap. Runs Claude itself as the coordinator with subagent executors in isolated git worktrees; for the standalone `arbor` CLI tool see references/arbor-upstream.md.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Understand how ideas evolved over time to find old solutions for new problems and avoid repeating past failures

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use before creative or constructive work (features, architecture, behavior). Transforms vague ideas into validated designs through disciplined reasoning and collaboration.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to discover, evaluate, or prioritize App Store keywords. Also use when the user mentions "keyword research", "find keywords", "search volume", "keyword difficulty", "keyword ideas", or "what keywords should I target". For implementing keywords into metadata, see metadata-optimization. For auditing current keyword performance, see aso-audit.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze a project's past Codex sessions, memory files, and existing local skills to recommend the highest-value skills to create or update. Use when a user asks what skills a project needs, wants skill ideas grounded in real project history, wants an audit of current project-local skills, or wants recommendations for updating stale or incomplete skills instead of creating duplicates.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Stress-tests ideas by surfacing assumptions, counterarguments, and confidence gaps. Use when evaluating claims, proposals, plans, or decisions that need rigorous intellectual scrutiny.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill whenever the user asks to inspect JoCoHunt, 조코헌트, jocohunt.jocoding.io products, ideas, rankings, makers, public security headers, or wants a CLI workflow for the Korean builder community. It runs the local `jocohunt` Go CLI, including authenticated product submission when explicitly requested.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill before any creative or constructive work (features, components, architecture, behavior changes, or functionality). This skill transforms vague ideas into validated designs through disciplined, incremental reasoning and collaboration.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use before creative or constructive work (features, architecture, behavior). Transforms vague ideas into validated designs through disciplined reasoning and collaboration.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate project ideas via creative constraints.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Structured validation framework that scores product ideas. Use when evaluating problem severity, willingness-to-pay, or founder-market fit. For market intelligence, see market-research.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.