documentation
Documentation standards, writing style, markdown conventions, and sources of truth for ADAMANT iOS. Use when writing or updating documentation.
Documentation standards, writing style, markdown conventions, and sources of truth for ADAMANT iOS. Use when writing or updating documentation.
CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating or editing any Svelte component (.svelte) or Svelte module (.svelte.ts/.svelte.js). If possible, this skill should be executed within the svelte-file-editor agent for optimal results.
Figma-to-code translation, design tokens, spacing/typography scales, responsive breakpoints, and design system bridge patterns.
Generate structured plan files for large tasks. Use when starting a big feature, refactoring, or multi-phase work. Creates plans/<task>-plan.md with phases, acceptance criteria, and open questions. After each phase, generates completion docs.
Multi-page deep crawling - documentation sites, wikis, knowledge bases
Proje bilgisini 4 katmanli yapida organize et. Aktif projeler, sorumluluk alanlari, referans kaynaklar ve arsiv. Progressive summarization ile bilgiyi katman katman ozumse. Second brain pattern'i ile codebase bilgisini yapilandir.
Problem-solving strategies for proof theory in mathematical logic
Document modeling, aggregation pipeline, indexing strategy, change streams, and multi-document transactions.
Use this skill when context compression is imminent, when resuming a session, or when preserving critical decisions across long tasks. Provides a durable notepad that survives compaction and lets any agent pick up exactly where the previous context left off.
External research workflow for docs, web, APIs - NOT codebase exploration
OpenAI Codex CLI + Claude Code (Hizir) birlikte kullanim rehberi. Is dagitim pattern'leri, GitHub Actions workflow ornekleri, review dongusu ve iki AI yazilim asistaninin guclu yanlarini birlestiren orchestration stratejileri.
Create or revise documentation for the simple-stack repository, especially MDX guides and API reference content under www/src/content/docs/. Use when asked to write docs, restructure guides, add examples, or enforce documentation tone, structure, and code highlighting conventions.
IWSDK project planning and best practices guide. Use when planning new IWSDK features, designing systems/components, reviewing IWSDK code architecture, or when the user asks about IWSDK patterns, ECS design, signals, or reactive programming in this codebase.
Multi-step web research, compilation, and synthesis workflow. Scrapes multiple sources, cross-references claims, and produces a structured research brief.
Reviews user-facing microcopy against content design guidelines and provides clear, actionable recommendations.
Use when given a Linear issue ID, URL, identifier, or project name/URL to analyze and plan work. For issues, fetches the issue, classifies it, explores relevant code, proposes an approach, and orchestrates the right skills. For projects, fetches the project with milestones and issues, builds a prioritized execution plan, and systematically works through issues respecting project structure and dependencies.
Review design documents using a multi-agent expert panel. Use when reviewing architecture docs, design proposals, data model designs, feasibility assessments, or technical RFCs. Also use when the user says "review this design", "get feedback on this doc", "launch a review panel", "stress-test this design", or wants expert opinions on a design document before implementation. Covers internal design docs, ag-shared design decisions, and PRD-adjacent technical documents.
Create a vocabulary learning lesson MulmoScript with multi-section structure (word display, examples with voice_over, explanation, review with translation). Use when the user wants to create vocabulary learning content with a lesson/presentation-style format rather than chat-style.