Need Developer Experience Treated as Product Discipline
Documentation efforts are treated as a publishing exercise rather than a product discipline that actively enables and teaches developers.
Take Control Of Your Signals — Become a Naftiko Design Partner Today!
Persona Story:
Pat, the head of platforms, sees documentation efforts treated as a publishing exercise rather than a product discipline that actively enables and teaches developers.
Problem Context
- Documentation roadmaps prioritize streamlining and accessibility
- Teams optimize for “what’s documented” rather than “what developers can successfully do”
- Developer populations are diverse (new hires, junior devs, partner engineers, domain experts)
Problem Impact
- Documentation becomes “complete” but not effective
- Inconsistent developer outcomes: experts succeed, novices stall
- Slower adoption of new capabilities because learning curves are not product-managed
Naftiko Today
- Agent Skills exposure groups MCP tools into business-level skills with auto-exposed HTTP APIs for discovery and download, turning documentation into an interactive product
- The 10-step tutorial and reference examples treat onboarding as a guided product experience rather than a static documentation dump
- Backstage integration provides a self-service developer portal with capability template scaffolding and one-click creation, productizing the integration workflow
- Executable YAML specs mean developers experience capabilities by running them, not just reading about them
Naftiko Tomorrow
- Starter templates (Second Alpha) would provide curated, opinionated starting points for common integration patterns, lowering the learning curve
- VS Code Agent Plugin with Naftiko Skills preset (Second Alpha) would embed guided capability authoring directly in the IDE where developers already work
- Capability scaffolding from existing APIs (Second Alpha) would let teams generate working capabilities from what they already have, reducing time-to-first-success
- TechDocs integration (First Beta) would embed capability documentation directly in Backstage, making docs a living part of the platform product