'developer' 검색 결과

새 기능이나 제안을 PM, 설계, 개발, QA의 네 관점에서 동시에 검토합니다. 역할별 우려와 첫 행동을 정리하고 공통점과 의견 충돌을 요약합니다.

• 새 기능을 네 역할의 관점에서 검토
• 구현 전 제안의 우려 사항 확인
• 새로운 업무의 첫 행동 정리

Generate website design references as separate horizontal images for each section. Keep a consistent palette while varying layouts, spacing, imagery, and calls to action, giving developers or coding agents concrete visual references for implementation.

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

• Create section-by-section landing page design references
• Explore different hero layouts
• Share visual references with developers

Prepare a design handoff package for a developer using Claude Code. It documents screen layouts, visual details, interactions, and state requirements in a README.md, alongside reference files for implementation in the target app.

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

• Handing HTML prototypes to a developer
• Documenting precise visual details for implementation
• Explaining screen interactions and state requirements

Maintain a Chinese independent developer project list by reviewing comments, issues, and pull requests. Check duplicate URLs and submission eligibility, add projects to the appropriate README, merge contributions, and reply with the listing result.

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

• Review new project submissions
• Check duplicate product URLs
• Place projects in the appropriate list

Turn API code into documentation covering available operations, inputs, outputs, authentication, and errors. Add practical request examples and usage guides, with OpenAPI specifications or Postman collections where possible to help developers explore and use the API.

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

• Document a new API from its code
• Update documentation after API changes
• Prepare API guides for new developers or external users

Turn API code into documentation covering endpoints, inputs, authentication, responses, and errors. Add request examples in multiple languages and usage guides to help developers understand and start using the API.

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

• Writing documentation for a new API
• Updating API documentation after code changes
• Preparing API guides for new developers or external users

Create a consistent UI design system from brand colors. Generate design tokens, reusable values for colors, typography, and spacing, and support component documentation, responsive layout calculations, accessibility considerations, and clear handoff materials for developers.

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

• Generate shared design values from brand colors
• Standardize typography and spacing across screens
• Plan layouts for different screen widths

Plan a portfolio website that helps potential employers or clients understand your work and contact you. Covers site structure, project presentations, case studies explaining decisions and results, personal branding, and mobile usability.

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

• Planning a developer or designer portfolio
• Turning projects into detailed case studies
• Improving paths from project pages to contact

Turn a design into a developer handoff document covering layout, shared design settings, component options, interactions, and screen-size behavior. Include loading and error states, animation details, and accessibility notes to clarify implementation requirements.

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

• Preparing a design for developer handoff
• Documenting layout changes across screen sizes
• Specifying loading, empty, and error states

Build and troubleshoot ChatGPT apps with an MCP server that exposes tools and an optional interactive widget. Use current official documentation and examples to create scaffolds, configure security settings, and guide local validation and deployment when requested.

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

• Create a ChatGPT app scaffold from an official example
• Design tools and connect an MCP server to a widget
• Refactor or troubleshoot an existing Apps SDK app

Helps individual developers get started on Google Cloud by checking local tools and authentication, selecting or creating a project, and linking billing. It verifies the setup and directs users to specialized guides for their first deployment.

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

• Setting up a first Google Cloud project
• Reusing an existing project for development
• Checking authentication and billing setup

Design reusable Figma components, flexible layouts, and shared design systems. Get guidance on managing colors and spacing, supporting themes and screen sizes, and preparing clear specifications and assets for developers.

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

• Organizing reusable components and their variants
• Building layouts that adapt to different screen widths
• Managing shared colors, spacing, and light or dark themes

Investigate software errors, version conflicts, and API questions across official documentation, GitHub, technical Q&A, and Chinese developer communities. Results distinguish matching errors, source authority, and reported environments, giving you documented leads and next checks for debugging.

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

• Find existing reports of the same error
• Investigate package and runtime version conflicts
• Look up API usage in documentation and Q&A

Turn a design into a developer handoff document covering layout, shared design settings, component options, interactions, and screen-size behavior. Include loading and error states, animation details, and accessibility notes to clarify implementation requirements.

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

• Preparing a design for developer handoff
• Documenting layout changes across screen sizes
• Specifying loading, empty, and error states

Build, refactor, and troubleshoot ChatGPT apps with an MCP server, which exposes tools to the assistant, and an interactive widget. Use official documentation and examples to plan tools, scaffold code, configure security settings, and validate local operation.

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

• Scaffolding a ChatGPT app with a server and widget
• Planning app tools and their inputs
• Refactoring an existing Apps SDK demo

Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals. Use PROACTIVELY for API documentation or developer portal creation.

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

Design and implement Internal Developer Platforms (IDPs) with self-service capabilities, golden paths, and developer experience optimization. Covers platform strategy, IDP architecture (Backstage, Port), infrastructure orchestration (Crossplane), GitOps (Argo CD), and adoption patterns. Use when building developer platforms, improving DevEx, or establishing platform teams.

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

Use when you need to create a DEVELOPER.md file for a Maven project — combining a fixed base template with dynamic sections derived from allowlisted Maven POM structure, including a Plugin Goals Reference, Maven Profiles table, and Submodules table for multi-module projects. This should trigger for requests such as Create DEVELOPER.md; Generate DEVELOPER.md; Maven project documentation; Add Maven documentation; Plugin goals reference. Part of Plinth Toolkit

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

Turn developer love into revenue by enabling champions and choosing a GTM model. Use when developers adopt the free tier but nobody pays, when the user is cold-selling the VP instead of arming the developer, or when picking between open-source, PLG, inbound, and sales-led.

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

Klaviyo API and developer integration expertise. Event tracking, SDKs, webhooks, rate limits, OAuth, catalog sync, and code patterns. Use when the user asks about Klaviyo API, integrating with Klaviyo, tracking events, building custom integrations, webhook handling, or developer implementation. For marketing strategy, flow optimization, and campaign auditing, see the klaviyo-analyst skill.

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

Create developer-friendly presentations using Slidev. Build Vue-powered slides with live code execution, syntax highlighting, and diagrams. Use when a user asks to create a presentation, build slides, make a tech talk, create a slide deck, or prepare a developer presentation.

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

GitHub 解封 — 账号封禁/限制/恢复的领域操作系统。覆盖：(a) GitHub 官方政策体系 (TOS / 可接受使用政策 / Trust & Safety 执行模式 / 公开申诉路径 / 受制裁地区解读)；(b) 封号原因诊断学 (spam / abuse / 制裁误标 / 2FA 丢失 / ToS 违规 / 账号劫持误判 / ban evasion 等子类型 + 症状→原因映射 + 自我分诊压测)；(c) 申诉实操 craft (写一封能让 T&S 快速判误伤的英文申诉信 + 升级阶梯 + 法务介入边界 + Don'ts)；(d) 制裁与合规硬边界 (OFAC SDN 名单 / 哪些国家或地区真不可达 / VPN 误判路径 / 中国大陆不是美国制裁地区的反复重申)；(e) 中国大陆开发者特别处境 (sanctioned region 误标 + SMS 验证不支持 +86/+852 + Gitee/GitLab/Codeberg/JihuLab 备用迁移 + 私有自托管 Gitea/Forgejo)；(f) 真实案例库 (~30+ 公开案例分类拆解：误伤 / 真违规 / 制裁误标三类各自赔率与申诉成功路径)。伦理锚绝不软化：不教 ban evasion / 不教撒谎式申诉 / 真违规承认改进 / 丢 2FA 无恢复因子则诚实告知 / 中国制裁误标靠申诉不靠换 VPN / 申诉 6 个月窗口必算清 / 约 3% (业内估) 真违规恢复 vs 约 79% (业内估) 误伤申诉成功率分层标。 (GitHub Account Reinstatement — the domain operating system for GitHub (and analogous platform) account suspension, restriction, appeal, and recovery. Covers: (a) GitHub official policy architecture (TOS / Acceptable Use Policies / Trust & Safety enforcement patterns / public appeals pathways / sanctioned-region interpretation); (b) suspension-cause diagnostics (spam / abuse / sanctions mis-flag / 2FA loss / ToS violation / account hijack false-positive / ban evasion taxonomy + symptom→cause mapping + self-triage pressure test); (c) appeal craft (writing an English appeal letter that gets T&S to fast-track a false-positive ruling + escalation ladder + legal-engagement boundary + Don'ts); (d) sanctions and compliance hard boundaries (OFAC SDN list / which countries/regions are truly unreachable / VPN false-positive paths / China is NOT a US-sanctioned region — repeated emphasis); (e) mainland China developer special circumstances (sanctioned-region mis-flag + SMS verification does not support +86/+852 + Gitee/GitLab/Codeberg/JihuLab fallback migration + self-hosted Gitea/Forgejo); (f) real-case library (~30+ public cases with categorized analysis: false-positive / genuine violation / sanctions mis-flag, each with win-rate and appeal success path). Ethical anchors absolutely not softened: do NOT teach ban evasion (creating new accounts turns a temp ban into a permanent one — the single biggest mistake); do NOT teach social engineering or lying in appeals (misuse + actually confirms violation); genuine violations: admit + improve beats denial; lost 2FA + no recovery factor → do not pretend recovery is possible; China sanctioned-region mis-flag → fix via appeal, not repeated VPN switching; appeal form 6-month window must be counted carefully; historical 约 3% (业内估) genuine-violation recovery vs 约 79% (业内估) false-positive appeal success rate stratification must be honestly labeled. Anti-samples (explicitly describe harm, never endorse): developer permabanned for ban evasion / open-source team org-banned for personal attacks in public issues / cases where repeated VPN switching escalated risk-control severity.) Master OS — automated mastery of GitHub Account Reinstatement — the domain operating system for GitHub (and analogous platform) account suspension, restriction, appeal, and recovery. Covers: (a) GitHub official policy architecture (TOS / Acceptable Use Policies / Trust & Safety enforcement patterns / public appeals pathways / sanctioned-region interpretation); (b) suspension-cause diagnostics (spam / abuse / sanctions mis-flag / 2FA loss / ToS violation / account hijack false-positive / ban evasion taxonomy + symptom→cause mapping + self-triage pressure test); (c) appeal craft (writing an English appeal letter that gets T&S to fast-track a false-positive ruling + escalation ladder + legal-engagement boundary + Don'ts); (d) sanctions and compliance hard boundaries (OFAC SDN list / which countries/regions are truly unreachable / VPN false-positive paths / China is NOT a US-sanctioned region — repeated emphasis); (e) mainland China developer special circumstances (sanctioned-region mis-flag + SMS verification does not support +86/+852 + Gitee/GitLab/Codeberg/JihuLab fallback migration + self-hosted Gitea/Forgejo); (f) real-case library (~30+ public cases with categorized analysis: fa

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

Build and grow developer and user communities from scratch — covering ambassador programs, community-led growth (CLG), event operations, content strategy, and health metrics. Grounded in real playbooks from Notion, Lovable, AFFiNE, ClickUp, Asana, and Lark. Use when: building a community for an open-source project, SaaS product, or brand; recruiting and managing ambassadors or community leaders; planning community events (online/offline meetups, AMAs, hackathons); designing ambassador tier/points systems; setting community health KPIs; launching a Build-in-Public strategy; setting up Discord, Slack, or Lark communities; running developer relations (DevRel); or when the user asks about community operations, ambassador programs, CLG, user advocacy, KOC/KOL cultivation, UGC flywheels, community monetization, or any variation of "how do I grow my community".

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

You launched an ambassador program. 3 applications. One ghosted after week 2. Should you lower the bar? Offer more perks? Spam influencers? This gives you the community & ambassador operations SOP with volunteer, paid tutorial creator and code-contributor tracks — from pre-launch checklist to recruitment to tiered management to retention to governance. Built from Notion (20M users, real ambassador interviews), AFFiNE (60K stars), Asana, and ClickUp programs. By @WeiYipei. 🇨🇳 你搞了个大使计划。来了3个申请。一个第二周就消失了。该降门槛？加福利？群发KOL？这份SOP给你从启动前置条件到招募到留存到治理的完整社区/大使运营方法论。基于 Notion（2000万用户，大使真实访谈）、AFFiNE（60K stars）、Asana、ClickUp 实战案例。 🇯🇵 アンバサダープログラムを立ち上げた。応募3件。1人は2週間で消えた。基準を下げる？特典を増やす？このSOPは、事前チェックリストから採用、段階管理、リテンション、ガバナンスまでの完全なコミュニティ＆アンバサダー運営フレームワークを提供します。Notion（2000万ユーザー）、AFFiNE（60K stars）の実例から構築。 🇰🇷 앰배서더 프로그램을 시작했습니다. 지원 3건. 하나는 2주 만에 사라졌습니다. 기준을 낮출까요? 이 SOP는 사전 체크리스트부터 모집, 단계별 관리, 리텐션, 거버넌스까지 완전한 커뮤니티 & 앰배서더 운영 프레임워크를 제공합니다. Notion(2000만 사용자), AFFiNE(60K stars) 실전 사례에서 구축. Triggers: "ambassador program" | "community building" | "community management" | "DevRel" | "developer relations" | "community growth" | "大使计划" | "社区运营" | "社区搭建" | "コミュニティ運営" | "アンバサダー" | "커뮤니티 운영" | "앰배서더" | "open source community" | "user retention"

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