'write' 검색 결과

Expert knowledge of MEDL (Medlemskapsregister) integration in melosys-api. Use when: (1) Debugging MEDL period creation/update failures, (2) Understanding data mapping between domain entities and MEDL API, (3) Working with saga steps that write to MEDL (LagreMedlemsperiodeMedl, LagreLovvalgsperiodeMedl), (4) Understanding MEDL enums (PeriodestatusMedl, LovvalgMedl, DekningMedl, GrunnlagMedl), (5) Troubleshooting Article 13 provisional vs final period logic.

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

Expert knowledge of the saksflyt saga pattern implementation in melosys-api. Use when: (1) Debugging or modifying process flows (Prosessinstans, ProsessType, ProsessSteg), (2) Understanding async step execution and locking mechanisms (låsReferanse), (3) Investigating race conditions, OptimisticLockingException, or entity overwrites, (4) Moving event listeners to saga steps to avoid sync/async conflicts, (5) Adding new process types or steps, (6) Deciding whether to use @DynamicUpdate on entities.

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

Resolve and enrich Knowledge people, companies, projects, and concepts during an authorized ingestion or entity update, with sourced State, timelines, and back-links. Read-only identity questions do not authorize writes.

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

Decides where a standing rule lives and builds the config Claude reads before work — CLAUDE.md, AGENTS.md, Project instructions and knowledge files, profile preferences, .claude/rules and agents, hooks, .mcp.json. Trigger on 'where should this rule live', 'set up a Claude Project', 'write or trim my CLAUDE.md', 'my rules get ignored', 'audit my setup for bloat or stale status', 'cut my CLAUDE.md token cost', 'add what we learned to CLAUDE.md', or rigwright (place, build, audit, learn, slim, refresh). Permissions, hook safety and config maps are gatewarden's; skills, skillwright's; unattended work, agentwright's; a block's wording, promptwright's.

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

Researches a question to something usable — a verdict with a flip condition, a versioned playbook or a graded report — every claim tagged by evidence. Trigger on which X should I pick (even from pasted pages), is Y worth it, compare A vs B, go/no-go, research this, deep research, fact-check a doc, write or merge a reference guide or playbook, grade a research report, read a bot-blocking source (Reddit, YouTube, X), or map an unfamiliar repo before contributing (entry points, flows, where to change X); or say researchscribe (verdict, playbook, research, verify, sources, map, refresh). Code review is engineering tooling's; fiction canon is lorescribe's; messages commscribe's; prompt model picks promptwright's; skill niches skillwright's; config rigwright's; brands brandscribe's.

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

Vets third-party skills, plugins, MCP servers, GitHub Actions and model weights before install, with a verdict (PASS, CONDITIONAL, HOLD, FAIL) and install terms. Trigger on any should-I-install question, even with its files or hooks pasted in or a scan already clean; is this skill safe, vet this MCP server, check this GitHub Action, is this checkpoint safe or commercially usable, what does this installer write, a licence check before a fold-in, what changed in a plugin update; or say trustwarden (vet, revet, terms, refresh). Uses skillspector, zizmor, pinact and Scorecard when present; lists files no scanner read. Runtime permissions are gatewarden's; secrets shieldwarden's; your own skills skillwright's; sandboxing a download hypervrunner's.

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

Runs the test-first build loop (spec, plan, thin slices, failing test first, verify, commit) for a Godot 4 game in GDScript or C# first; in a TypeScript, Python or other repo when test-first, slices or a reproduce-first fix is asked for. Trigger to build or add a game feature, mechanic, stat, system or milestone, even when told to test later; to turn a spec or grill record into slices; to fix a game bug from a reproduction, one hypothesis at a time; on "write the test first", "what's the next slice", "is this slice done" or "is this milestone ready to exit"; or say slicesmith (spec, plan, slice, fix, exit). Run proof and gate rulings are godotsmith's; diff review a review tool's; repo maps researchscribe's; art pixelsmith's; audio soundsmith's; interviews grillwright's; fan-out dispatchwright's.

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

Directs screens and proves they fit — game menus and HUD, web dashboards, single-page artifacts, store-page layouts and plugin panes. Writes the design brief (layout, hierarchy, spacing and type scales, every state, focus and hit size, a check against generic-looking output) and probes the rendered page at phone-to-desktop widths in every theme. Trigger to design or lay out a menu, HUD, dashboard, settings screen or panel, or review its mockup before the build; when a page scrolls sideways on a phone, text is clipped or a dark theme breaks; to check that a page or pane fits from 320 to 1440 px in light and dark; for UI direction before a build, even when nobody says design; or say uismith (direct, probe, fit-first audit). The probe needs optional Playwright. A critique, scored review or brand pass of a built page, palettes and type are brandscribe's; sprites and icons pixelsmith's; Godot scene proof godotsmith's; words commscribe's.

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

Drives OBS Studio through its WebSocket, read-only by default, and turns recordings into clips, VOD cuts and chapters with FFmpeg. Trigger to audit an OBS setup; when a stream drops frames or lags; to switch a scene, mark a moment or save the replay buffer; to cut clips, burn in captions, normalize loudness or write chapters; when OBS shares a GPU; or say obsrunner (audit, check, set, mark, post, sheet, status, hold, release, refresh). Live work needs the user-installed obsws-python package. Never goes live, uploads or moderates chat. Caption files are whisperrunner's; thumbnails comfyrunner's; titles commscribe's; analytics duckrunner's.

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

Patterns for scaling read-heavy Convex apps to millions of users. Use when optimizing bandwidth, reducing query costs, fixing slow queries, creating digest tables, replacing reactive subscriptions with one-shot fetches, adding compound indexes, debouncing writes, rate-controlling backfills, or running npx convex insights. Trigger when users mention "scale", "bandwidth", "performance", "optimize", "slow queries", "expensive queries", "digest table", "denormalize", or "thundering herd" in the context of Convex.

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

Audits Convex performance for reads, subscriptions, write contention, and function limits. Use for slow features, insights findings, OCC conflicts, or read amplification.

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

Elite mobile app image-generation skill for creating premium, app-native screen concepts and flows. Designed for iOS, Android, and cross-platform mobile products. Prioritizes clean hierarchy, comfortably readable text, strong multi-screen consistency, controlled color palettes, non-generic creative direction, textured surfaces, image-led composition, tasteful custom iconography, and clean phone mockup framing. By default, screens should be shown inside a subtle premium iPhone or similar phone mockup with a visible frame, while the main focus stays on the app content itself. This skill generates images only. It does not write code.

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

Guide for when to use and when not to use return validators in Convex functions. Use this skill whenever the user is writing Convex queries, mutations, or actions and needs guidance on return value validation. Also trigger when the user asks about Convex type safety, runtime validation, AI-generated Convex code, Convex AI rules, Convex security best practices, or when they're debugging return type issues in Convex functions. Trigger this skill when users mention "validators", "returns", "return type", or "exact types" in the context of Convex development. Also trigger when writing or reviewing Convex AI rules or prompts that instruct LLMs how to write Convex code.

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

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.

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

Writing style guide for technical content, social media, blog posts, READMEs, git commits, and developer documentation. Optimized to avoid AI detection patterns. Use when writing any content beyond code.

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

Convex is the backend agents get right on the first try: an all-TypeScript reactive platform where the database, server functions, scheduling, file storage, auth, and realtime sync are one type-safe system, every function is a transaction, and `tsc` catches most mistakes before deploy. Ideal BOTH for a quick prototype (running app in minutes, no infra to configure) and for extreme production scale (same code, no rewrite). Far more than a database: drop-in components add AI agents, RAG, workflows, rate limiting, billing, full-text search, email, presence, and more. Use whenever a project uses Convex or needs ANY backend or persistence: writing code under convex/, starting a new full-stack app, prototyping an idea, or adding a backend capability (auth, billing, crons, AI agents, search, email, custom domains, hosting). Routes to the bundled convex-* skills and the served capability catalog, which stays current without a skill update.

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

Audit and harden a Convex app's authorization: identity-from-arg impersonation, missing per-document ownership checks, public queries leaking data by a client-supplied id, and writes into a parent/container the caller doesn't own. Scans for the 4 shapes, applies requireIdentity/requireOwner, verifies with tsc. TRIGGER on 'secure my app', 'audit auth/authz', 'who can access this data'. SKIP when there is no convex/ directory.

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

Write acceptance tests before unit tests to ensure you're building the right thing

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

Write clear, testable acceptance criteria in Given-When-Then format following INVEST principles and BDD best practices.

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

Toolkit for creating an entertainingly stupid README that manages to give off Tim & Eric, Steve Brule vibes while maintaining a level of technical acumen that is expected of a modern open source project. This skill applies when users request a silly or absurd README.

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

Write JavaScript code in the style of Dan Abramov, co-creator of Redux and React core team member. Emphasizes predictable state management, composition over inheritance, and developer experience. Use when building React applications or managing complex state.

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

Write-time code quality enforcement using Plankton — auto-formatting, linting, and Claude-powered fixes on every file edit via hooks.

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

Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.

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

A hard-edged writing style contract for timeless, forceful English prose without modern AI tics. Use when users ask for prose or rewrites that must be clean, exact, concrete, and free of AI cadence, filler, or therapeutic tone.

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