Loading...
Loading...
Found 19 Skills
Developer Experience specialist for tooling, setup, and workflow optimization. Use when setting up projects, reducing friction, improving development workflows, or automating repetitive tasks. Focuses on making development joyful and productive.
Use this skill when designing SDKs, writing onboarding flows, creating changelogs, or authoring migration guides. Triggers on developer experience (DX), API ergonomics, SDK design, getting-started guides, quickstart documentation, breaking change communication, version migration, upgrade paths, developer portals, and developer advocacy. Covers the full DX lifecycle from first impression to long-term retention.
Technical documentation specialist for API docs, tutorials, architecture docs, and developer experienceUse when "documentation, docs, readme, tutorial, api docs, guide, changelog, comments, openapi, documentation, api-docs, tutorials, readme, openapi, swagger, developer-experience, technical-writing, ml-memory" mentioned.
The craft of communicating technical concepts clearly to developers. Developer communications isn't marketing—it's about building trust through transparency, accuracy, and genuine utility. The best devrel content helps developers solve real problems. This skill covers technical documentation, developer tutorials, API references, changelog writing, developer blog posts, and developer community engagement. Great developer communications treats developers as peers, not leads to convert. Use when "documentation, docs, tutorial, getting started, API reference, changelog, release notes, developer guide, devrel, developer relations, code examples, SDK docs, README, documentation, devrel, tutorials, api-docs, developer-experience, technical-writing, getting-started, changelogs" mentioned.
OPT-IN skill. Send developer-experience feedback about the TomTom Maps SDK for JavaScript (@tomtom-org/maps-sdk) to its public GitHub repository, tomtom-international/maps-sdk-js, as an issue or a discussion. Use at the START of any work with the SDK to ask the developer once for permission (the tomtom-maps-sdk-js skill hands over here for that), and after that whenever the SDK gets in the way while building — the docs, types or AI skill did not say what was needed; the API cannot express what the developer asked for; the code that actually works differs from what the docs or examples showcase; or something is plainly broken. Also use when the developer says "report this", "send feedback", "file an issue", "tell TomTom", "stop sending feedback", or asks what feedback has been collected so far. Drafts a redacted report and posts it only after the developer approves that draft.
Live developer experience audit. Uses the browse tool to actually TEST the developer experience: navigates docs, tries the getting started flow, times TTHW, screenshots error messages, evaluates CLI help text. Produces a DX scorecard with evidence. Compares against /plan-devex-review scores if they exist (the boomerang: plan said 3 minutes, reality says 8). Use when asked to "test the DX", "DX audit", "developer experience test", or "try the onboarding". Proactively suggest after shipping a developer-facing feature. (gstack) Voice triggers (speech-to-text aliases): "dx audit", "test the developer experience", "try the onboarding", "developer experience test".
Benchmarks a competitor's developer relations motion from publicly observable signals - documentation and quickstart quality, open-source repository health, community size and responsiveness, Q&A tag activity, content cadence by format, event presence, hiring signals - and returns a gap plan with a close, ignore or counter verdict per row. Use whenever the user asks for a devrel competitive benchmark, a developer experience comparison, "how do we compare to <competitor> for developers", "what is <competitor> doing in devrel", a community size or content cadence comparison, or a docs comparison against rivals - even if they only say "why do they get more developers". Not for measuring your own program alone - use samber/developer-relations-skills@devrel-metrics.
Help users build strong engineering culture. Use when someone is improving developer experience, fostering technical excellence, designing engineering practices, or scaling an engineering organization.
When the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
Audits and rewrites a repository README so a developer who has never seen the project can tell what it is, why it beats the alternative, and run the first command inside a minute - every claim and the documented install verified against the source, the page ordered into a bail-fast funnel, badges that earn nothing pruned. Use whenever someone says "review my README", "my readme is bad", "write a README for this repo", "nobody understands what my project does", "repo first impression", "readme structure", "too many badges", or is preparing an open-source launch - even if they only call it the repo landing page. Not a profile README - use samber/developer-relations-skills@github-profile-optimization.
Improve developer experience, tooling, and workflows. Use when setting up projects or reducing development friction.
Use when a codebase, product, workflow, runtime, or organization needs purpose-first whole-machine stewardship: understand what the whole system is trying to produce, then improve the machinery, tooling, feedback loops, operability, and developer flow that let it produce that output.