57건 · 관련도순
Auri: assistente de voz inteligente (Alexa + Claude claude-opus-4-20250805). Visao do produto, persona Vitoria Neural, stack AWS, modelo Free/Pro/Business/Enterprise, roadmap 4 fases, GTM, north star WAC e analise competitiva.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find a direct path to structured data through ready-made workflows, data APIs, and indexes. Follow the search skill to discover and inspect tools, then the scrape skill to execute them.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive SEO/GEO/AEO analysis toolkit for optimizing content visibility across traditional search engines (Google, Bing), AI platforms (ChatGPT, Perplexity, Claude, Gemini, Grokipedia), answer engines (Google AI Overviews, Bing Copilot, featured snippets), voice assistants (Google Assistant, Siri, Alexa), and social media (Facebook, Twitter, LinkedIn, WhatsApp, Instagram). Analyzes HTML/Markdown/JSX files for metadata completeness, schema markup, keyword optimization, entity extraction, and generates multi-format audit reports with platform-specific recommendations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find and qualify new prospects with Firecrawl Alexandria people and company data: people by role, seniority, company, industry, size, location or technology, target accounts that match criteria, or the right contacts at companies, returned as a ranked, sourced table or CSV. Also extracts lead lists from a database or directory the user names, and refreshes a prospect list with only new matches. Use when the user wants a lead list, prospects, target accounts or the people to reach out to at companies that fit criteria. Not for enriching people or companies the user already supplied (use firecrawl-lead-research).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enrich and research the people and companies the user names or supplies with Firecrawl Alexandria data: background on a person, a professional profile URL to look up, whether someone still holds a role, missing columns in a table or CSV of people or companies, firmographics for company domains (industry, headcount, funding, location), and pre-call or meeting briefs. Use whenever the request is about specific named people or companies, even without the word enrich, since roles, headcount and funding change faster than training data. Not for finding new prospects (use firecrawl-lead-gen) or a company's published press, sales or support contacts (use firecrawl-business-contacts).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enrich and research the people and companies the user names or supplies with Firecrawl Alexandria data: background on a person, a professional profile URL to look up, whether someone still holds a role, missing columns in a table or CSV of people or companies, firmographics for company domains (industry, headcount, funding, location), and pre-call or meeting briefs. Use whenever the request is about specific named people or companies, even without the word enrich, since roles, headcount and funding change faster than training data. Not for finding new prospects (use firecrawl-lead-gen) or a company's published press, sales or support contacts (use firecrawl-business-contacts).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find and qualify new prospects with Firecrawl Alexandria people and company data: people by role, seniority, company, industry, size, location or technology, target accounts that match criteria, or the right contacts at companies, returned as a ranked, sourced table or CSV. Also extracts lead lists from a database or directory the user names, and refreshes a prospect list with only new matches. Use when the user wants a lead list, prospects, target accounts or the people to reach out to at companies that fit criteria. Not for enriching people or companies the user already supplied (use firecrawl-lead-research).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find a direct path to structured data through ready-made workflows, data APIs, and indexes. Follow the search skill to discover and inspect tools, then the scrape skill to execute them.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find a direct path to structured data through ready-made workflows, data APIs, and indexes. Follow the search skill to discover and inspect tools, then the scrape skill to execute them.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Somatic movement and whole-body retraining as Joseph Pilates designed it in the Contrology method and as Moshé Feldenkrais designed it in Awareness Through Movement and Functional Integration, with enough cross-reference to the broader somatics landscape (Alexander Technique, Hanna Somatics, Body-Mind Centering) that an agent can place a user into the right method. Covers the Pilates reformer and mat system, the six Pilates principles, the Feldenkrais ATM lesson structure, the nervous-system learning frame that distinguishes somatics from exercise, and the safety posture that matters for rehab populations. Use for queries about core training, rehab-adjacent movement, chronic pain patterns, and learning-based movement re-education.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design polychromatic ornamental patterns grounded in Alexander Speltz's classical ornament taxonomy. Builds on monochrome structural analysis by adding period-authentic color palettes, color-to-motif mapping, and rendering styles suited to painted, illuminated, and glazed ornament. Use when creating decorative designs where color is integral to the tradition (Islamic tilework, illuminated manuscripts, Art Nouveau), exploring how historical periods used color in ornament, or producing colored reference imagery for design, illustration, or educational materials.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design monochrome ornamental patterns grounded in Alexander Speltz's classical ornament taxonomy. Covers historical period selection, motif structural analysis, prompt construction for line art and silhouette rendering, and AI-assisted image generation via Z-Image. Use when creating decorative borders, medallions, or friezes in a single color, exploring historical ornament styles through generative AI, producing line art or pen-and-ink renderings of classical motifs, or generating reference imagery for design or educational materials.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate, score, and shortlist brand names through a guided interview. Use when the user says "name my brand", "help me name", "come up with a name", "naming ideas", "what should I call this", "brand name", "product name", "company name", "rename", "rebrand", or is stuck choosing between names. Self-contained and brand-agnostic: it does not read knowledge/, so it works for naming a brand-new venture, product, service, feature, or rebrand from scratch, before any brand context exists. Runs on Alexandra Watkins' SMILE and SCRATCH tests to generate and filter, Marty Neumeier's 7 criteria to score, and the Lexicon Branding method for sound symbolism and strategy. Asks the user questions before generating. For the positioning the name has to carry, see positioning-doc. For the message architecture built on top of it, see messaging-framework.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Opinionated house conventions for NestJS backends — module boundaries and layering, provider wiring and injection scopes, guards/interceptors/pipes/filters, DTOs and validation, domain exceptions, config, and the Nest 11 / Express 5 behaviour that compiles cleanly and fails at runtime. Use whenever the code is NestJS (`@nestjs/*` in package.json, or `@Module`/`@Injectable`/`@Controller`/`@Cron` in the file), including when the question sounds like plain TypeScript, an OOP refactor, a code review, or an ops problem — the Nest-specific answer differs from the generic one. Typical asks: scaffolding a module, adding a controller, provider, or endpoint, wiring an enhancer, a boot-time DI or circular-import failure, a response leaking entity fields despite `@Exclude()`, a cron job firing on every replica, upgrading NestJS, or reviewing a Nest diff. Not for plain Express or Fastify, Angular, frontend, SQL, or CI.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Capture a solved, verified problem as a durable learning in `docs/solutions/` so the next agent or engineer does not repeat the mistake or redo the investigation, and keep the `CONCEPTS.md` glossary in step. Use after a fix, debugging session, or design decision whose reasoning is not readable from the final code, tests, or existing docs — "document this", "write up what we learned", "capture this learning", "add it to solutions", "that worked, save it for next time". Writes nothing for routine fixes the code already explains. For auditing or cleaning up existing learnings, use `learn-with-docs-refresh`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit and maintain the learnings in `docs/solutions/` against the current codebase — fix drifted paths and links, merge overlapping docs, replace guidance the code no longer supports, delete obsolete docs, reconcile the `CONCEPTS.md` glossary, then report and commit. Also bootstraps `CONCEPTS.md` on request and, when asked, culls docs whose reasoning the code already explains. Use for "refresh the learnings", "audit docs/solutions", "are our solution docs still accurate", "clean up / prune the learnings", "create a CONCEPTS.md", or after a refactor, rename, migration, or dependency upgrade that likely invalidated documented solutions. Not for capturing a new learning — use `learn-with-docs`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply these opinionated Next.js conventions whenever writing or reviewing App Router code (14+): Server Components by default, where the 'use client' boundary belongs, the caching defaults that changed in Next 15, tag-based revalidation, treating Server Actions as public endpoints, the Metadata API, and next/image and next/font.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply these opinionated C# conventions whenever writing or reviewing C# 12 / .NET 8+ code: nullable enabled with warnings as errors, records and primary constructors, pattern matching over cast chains, the Result pattern for expected failures, async all the way with CancellationToken, IOptions config, IHttpClientFactory, and never returning EF entities from an API.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply these opinionated React conventions when writing React 18+ or 19 components: hooks patterns, Server Components, Suspense boundaries, state management, performance memoization, React 19 features (use, form actions).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply these opinionated Python 3.11+ conventions when writing Python in this codebase: type hints with mypy, async/await, pytest fixtures, dataclasses, Poetry packaging, production patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply these opinionated TypeScript conventions whenever writing or reviewing TypeScript: branded types for domain modeling, discriminated unions for state, `satisfies` over `as`, const objects instead of enums, type-only imports, and the strict tsconfig baseline beyond `strict: true`. Also use for monorepo project references and incremental build setup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Draft the QA scope and plain-language Given/When/Then test scenarios for a Jira ticket, built from the full ticket, the decisions made in its comments, and the actual code change read commit by commit (open PR, the ticket's merged PR, the branch against its base, or a named commit range). Saves a Markdown draft under docs/, iterates with the user, then posts it to the ticket as a new Jira comment only after explicit approval. Use on "QA scope for PROJ-123", "what should QA test", "write test scenarios for QA", "hand this ticket to QA", "prep the QA handoff", "gherkin scenarios for this ticket", or when a branch is ready for manual testing — even when the user only names the ticket or says "this branch".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn the git commits for a Jira ticket into a short, business-friendly implementation report and save it as local markdown. Use when the user wants to report finished work on a Jira ticket: a Jira report, update, or comment, a summary of their commits or changes for the ticket, or a note telling PM/QA what shipped.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply these opinionated .NET 8 architecture conventions whenever structuring or reviewing a backend service: clean architecture layering and which direction dependencies point, when CQRS with MediatR is worth it, cross-cutting concerns as pipeline behaviours, minimal APIs grouped by feature, keeping DbContext in Infrastructure, health checks and structured logging, WebApplicationFactory integration tests, and when AOT pays off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.