How do I install the Backstage App skill?

Run npx skillmds@latest add paulasilvatech/backstage-app-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Backstage App safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Backstage App?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Backstage App free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Backstage App?

paulasilvatech (@paulasilvatech) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Backstage App by paulasilvatech — Agent Skill

Name: Backstage App
Author: paulasilvatech

File contents

Backstage Application

These rules cover the adopter app under backstage/. App configuration is owned separately by the backstage-config instructions.

Conventions

Keep frontend composition in backstage/packages/app, backend composition in backstage/packages/backend, and reusable AI Chat behavior in its plugin package.
Register plugins and modules through supported Backstage extension points; do not import package internals.
Align @backstage/* dependencies with the release policy recorded by backstage.json and the root Backstage manifest.
Preserve package ownership: package code, tests, and exports stay in the package that owns the behavior.
Keep browser code free of server credentials, Node-only dependencies, and privileged integration logic.
Use the repository's current frontend/backend system; make compatibility shims explicit and local when legacy behavior must remain.
Prefer package public APIs and typed service contracts over cross-package relative imports.

Verification

The owning package's test, lint, typecheck, or build script covers the change.
Dependency changes remain version-aligned across Backstage workspaces.
Frontend bundles contain no secrets or backend-only configuration.

Do / Do Not

Do	Do not
Use package public APIs and execute the owning package checks.	Reach across package internals or claim an unrun build passed.
Preserve version alignment and frontend/backend boundaries.	Bundle secrets or backend-only configuration in browser code.

Checklist Before Opening a PR

The change matches this instruction's applyTo scope.
Package public APIs and workspace version alignment are preserved.
Focused test, lint, typecheck, or build checks pass.
Frontend output contains no secret or backend-only configuration.
No unrelated edits or unresolved placeholders remain.

---name: backstage-app-2description: Use when editing Backstage adopter-app composition, packages, dependency alignment, or package-owned tests.---# Backstage ApplicationThese rules cover the adopter app under `backstage/`. App configuration is owned separately by the `backstage-config` instructions.## Conventions- Keep frontend composition in `backstage/packages/app`, backend composition in `backstage/packages/backend`, and reusable AI Chat behavior in its plugin package.- Register plugins and modules through supported Backstage extension points; do not import package internals.- Align `@backstage/*` dependencies with the release policy recorded by `backstage.json` and the root Backstage manifest.- Preserve package ownership: package code, tests, and exports stay in the package that owns the behavior.- Keep browser code free of server credentials, Node-only dependencies, and privileged integration logic.- Use the repository's current frontend/backend system; make compatibility shims explicit and local when legacy behavior must remain.- Prefer package public APIs and typed service contracts over cross-package relative imports.## Verification- The owning package's test, lint, typecheck, or build script covers the change.- Dependency changes remain version-aligned across Backstage workspaces.- Frontend bundles contain no secrets or backend-only configuration.## Do / Do Not| Do | Do not || --- | --- || Use package public APIs and execute the owning package checks. | Reach across package internals or claim an unrun build passed. || Preserve version alignment and frontend/backend boundaries. | Bundle secrets or backend-only configuration in browser code. |## Checklist Before Opening a PR- [ ] The change matches this instruction's `applyTo` scope.- [ ] Package public APIs and workspace version alignment are preserved.- [ ] Focused test, lint, typecheck, or build checks pass.- [ ] Frontend output contains no secret or backend-only configuration.- [ ] No unrelated edits or unresolved placeholders remain.

Frequently asked questions

Backstage App