client-vs-internal

Classify app surfaces as client-facing, internal, or shared using docs/audience.md.

6|Updated May 29, 2026
One-click install
npx skills add https://github.com/fusebase-dev/fusebase-flow --skill client-vs-internal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: client-vs-internal
Source: https://github.com/fusebase-dev/fusebase-flow/tree/main/flow-skills/client-vs-internal
Command: npx skills add https://github.com/fusebase-dev/fusebase-flow --skill client-vs-internal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often apply the same complex design to both client-facing and internal app surfaces, leading to frustrated clients who can't navigate over-complex tools, or internal teams missing critical robust controls they need to work efficiently. This skill eliminates that misalignment by automatically classifying surfaces and applying the right design posture for each audience.

Core Features & Use Cases

  • Audience-based surface classification: Automatically categorizes app surfaces as client-facing, internal, or shared using pre-defined audience personas from docs/audience.md.
  • Tailored design posture application: Applies simplified, guided, trust-first design for client-facing surfaces, and full robust controls, power features, and admin affordances for internal surfaces.
  • Mismatch flagging: Identifies and corrects design mismatches like over-complex client UIs or stripped-down internal tools missing necessary functionality.
  • Use Case: When building a customer support portal and an internal admin dashboard for the same product, this skill ensures the client portal is intuitive and easy to use while the admin dashboard has all the advanced controls your team needs.

Quick Start

Ask the AI to classify your new customer onboarding portal as client-facing and apply the appropriate simplified, guided design posture for that audience.

Frequently Asked Questions about client-vs-internal

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to align UI design posture for different app audiences?

To classify app surfaces and apply design postures, define audience personas in docs/audience.md, then have the system automatically categorize surfaces and enforce audience-appropriate guardrails during design, build, and review phases.

How do I prevent over-complex UI in client-facing app surfaces?

Prevent over-complex client-facing UI by applying an audience classification that enforces simplified, guided, trust-first design guardrails, automatically flagging and correcting complexity mismatches for customer-facing surfaces.

Does audience classification for internal tools require predefined personas?

Yes, audience classification for internal tools requires predefined audience personas stored in docs/audience.md to accurately categorize surfaces and apply full robust controls, power features, and admin affordances for internal teams.

How do I flag design mismatches between client-facing and internal surfaces?

Flag design mismatches by automatically classifying app surfaces against audience personas, identifying over-complex client UIs or stripped-down internal tools missing necessary functionality, and correcting them with appropriate design postures.

When should I use different design guardrails for shared app surfaces?

Use different design guardrails for shared app surfaces when both client and internal audiences interact with the same surface, ensuring the design posture balances simplified guided flows with necessary robust controls without causing complexity mismatches.