backy-frontend-desing-template

Backy frontend design template super-skill. Use for opinionated reusable visual templates for reports, quarterly reviews, editorial decks, research videos, and cinematic layouts. Routes across 9 Open Design template capabilities without installing them as 9 separate top-level skills.

Jump to install

Repository: varshneydevansh/backy
Last source activity: May 26, 2026 at 15:45
Detected SKILL.md language: English
Stars: 4
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/varshneydevansh/backy --skill backy-frontend-desing-template

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

12 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

Backy Frontend Desing: Template

Use this when the user asks for opinionated reusable visual templates for reports, quarterly reviews, editorial decks, research videos, and cinematic layouts.

This is a compact router over 9 Open Design template capabilities. Keep the top-level context small: start with the catalog, then load only the exact source reference files needed for the request.

Workflow

Read references/catalog.md to pick one primary capability and, if useful, one support capability.

Read only the matching file(s) from references/source/. Do not bulk-load every source file.

Apply the source skill's constraints, but keep the repo's existing architecture and design system unless the user explicitly asks for a new direction.

For UI work, verify real rendered output when a local app or HTML artifact exists. Use screenshots or browser checks for responsive and visual claims.

If the requested work crosses modes, combine this with the relevant sibling skill, for example backy-frontend-desing-design-system plus backy-frontend-desing-prototype.

Capability Map

8-bit-orbit-video-template -> references/source/8-bit-orbit-video-template.md

after-hours-editorial-template -> references/source/after-hours-editorial-template.md

digits-fintech-swiss-template -> references/source/digits-fintech-swiss-template.md

editorial-burgundy-principles-template -> references/source/editorial-burgundy-principles-template.md

field-notes-editorial-template -> references/source/field-notes-editorial-template.md

html-ppt-retro-quarterly-review -> references/source/html-ppt-retro-quarterly-review.md

swiss-creative-mode-template -> references/source/swiss-creative-mode-template.md

swiss-user-research-video-template -> references/source/swiss-user-research-video-template.md

weread-year-in-review-video-template -> references/source/weread-year-in-review-video-template.md

Backy Defaults

Prefer distinctive, production-grade UI over generic AI template structure.

Use real content and data from the user or project. Do not invent metrics, logos, testimonials, or product claims.

Keep typography, spacing, interaction states, and responsive behavior as first-class acceptance criteria.

When source skills conflict, choose the stricter visual QA rule and the simpler implementation.

For existing products, improve the current surface instead of replacing product structure wholesale.