write
무료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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
6천건 · 관련도순
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill enforces Sentry's blog writing standards across every post — whether you're helping an engineer write their first blog post or a marketer draft a product announcement.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Sentry Voice tones.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit and rewrite content to remove 21 categories of AI writing patterns with a 43-entry replacement table
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Translates or rewrites Chinese text into English using a 'critical dialogue' tone, characterized by engaging questions, analytical commentary, and a conversational flow while preserving citations and facts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drafts formal explanation letters for Canadian Study Permit applications by structuring the argument around program attractiveness, background relevance, choice rationale, and family benefits.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze and optimize tweets for maximum reach using Twitter's open-source algorithm insights. Rewrite and edit user tweets to improve engagement and visibility based on how the recommendation system ranks content.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write competitive research proposals for NSF, NIH, DOE, and DARPA. Agency-specific formatting, review criteria, budget preparation, broader impacts, significance statements, innovation narratives, and compliance with submission requirements.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architect...
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
自动从知乎热榜选题、调用 AI 生成原创回答并保存为草稿,支持自定义话题关键词、写作风格和批量生成。 Draft Zhihu answers automatically: picks hot questions, generates original answers via AI, and saves them as drafts — with custom topic filters, writing style, and batch support. Never publishes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Complete SEO + GEO (Generative Engine Optimization) system for SaaS companies wanting to rank on both Google and AI search engines (ChatGPT, Perplexity, Gemini, Claude). Use this skill whenever the user asks about SEO strategy, keyword research, content planning, writing SEO-optimized articles, auditing their search performance, creating a content calendar, analyzing competitors, or optimizing for AI search visibility. Trigger on: "seo", "keyword research", "content calendar", "rank on google", "search traffic", "write an article", "blog post", "serp", "backlinks", "competitor analysis", "content cluster", "seo audit", "geo optimization", "ai search", "search console", "organic traffic", "content strategy", "publish article", "seo setup", "ranking", "impressions", "ctr", "meta description", "schema markup", "faq schema". Also trigger when a user wants to set up their SaaS blog SEO from scratch, analyze their current rankings, or create a publishing workflow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build and run multi-agent content production teams on OpenClaw with single-repo architecture, symlink-based file sharing, role-specialized AGENTS.md, and automated review-fix-score loops. Use when: (1) Setting up a team of 3+ agents with writer/reviewer/scorer/fixer roles for content creation, (2) Creating a quality-controlled publishing pipeline, (3) Bootstrapping agent workspaces with symlinks and tool configs from scratch, (4) Running multi-round review→fix→score cycles until a quality threshold is met, (5) Debugging agent spawn permissions, tool-call loops, or symlink issues. Based on real production experience building a 6-agent content team (2026-03-30).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.