playbooks

home / skills / dexploarer / hyper-forge / developer-portal-generator

developer-portal-generator skill

/.claude/skills/developer-portal-generator

This skill helps you generate developer portals using Backstage or custom solutions, accelerating setup and ensuring consistent documentation and tooling.

npx playbooks add skill dexploarer/hyper-forge --skill developer-portal-generator

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.0 KB
---
name: developer-portal-generator
description: Create developer portals using Backstage or custom solutions
allowed-tools: [Read, Write, Edit, Bash, Grep, Glob]
---

# developer portal generator

Create developer portals using Backstage or custom solutions

## When to Use

This skill activates when you need to create developer portals using backstage or custom solutions.

## Quick Example

```yaml
# Configuration example for developer-portal-generator
# See full documentation in the skill implementation
```

## Best Practices

- ✅ Follow industry standards
- ✅ Document all configurations
- ✅ Test thoroughly before production
- ✅ Monitor and alert appropriately
- ✅ Regular maintenance and updates

## Related Skills

- `microservices-orchestrator`
- `compliance-auditor`
- Use `enterprise-architect` agent for design consultation

## Implementation Guide

[Detailed implementation steps would go here in production]

This skill provides comprehensive guidance for create developer portals using backstage or custom solutions.

Overview

This skill generates developer portals tailored for organizations using Backstage or custom solutions. It streamlines portal scaffolding, configuration, and extension wiring to surface services, components, and documentation. The output accelerates developer onboarding and centralizes tooling, catalogs, and CI/CD links.

How this skill works

The generator inspects repository metadata, service manifests, and infrastructure descriptors to build a catalog and navigation model. It produces Backstage-compatible configuration and optional custom portal scaffolds, wiring authentication, search, and plugin integrations. It can export sample docs, example components, and starter templates to jump-start adoption.

When to use it

  • Bootstrapping a new developer portal for a teams-first platform
  • Migrating catalogs and service metadata into Backstage
  • Creating a custom portal when Backstage does not meet specific UX or integration needs
  • Standardizing service documentation and onboarding flows across projects
  • Rapid prototyping of a portal to validate developer experience changes

Best practices

  • Adopt a standardized metadata model for services and components to feed the portal
  • Document portal configuration and extension choices alongside code repositories
  • Integrate single sign-on and role-based access to match org policies
  • Automate catalog syncs and CI/CD links to keep listings current
  • Start with a minimal set of plugins, then iterate based on usage data

Example use cases

  • Generate a Backstage instance with a populated software catalog from existing microservices
  • Create a custom portal for a specialized game-engine asset pipeline with embedded 3D previews
  • Migrate artifact and pipeline links from scattered README files into a searchable portal
  • Provide developer onboarding flows with step-by-step guides and sample code for new hires
  • Build a plugin scaffold to surface runtime metrics and deployment status directly in the portal

FAQ

Does this support both Backstage and fully custom portals?

Yes. The skill can emit Backstage configuration and scaffolding or produce custom portal templates tailored to specific UX and integration needs.

What inputs does the generator need?

It works best with repository manifests, service metadata, OpenAPI specs or typed component descriptors, and CI/CD pipeline references to populate the catalog.

Can it integrate authentication and existing plugins?

Yes. It can wire common SSO providers and configure standard Backstage plugins, with options to extend or swap implementations.