Skills shape
📦

shape

v2.1.1 Content revision r1 Safe ⚙️ External commands

Plan UX Before Building

Teams often build interfaces before clarifying user goals, states, and constraints. This skill guides discovery and produces a design brief for implementation.

Supports: Claude Codex Code(CC)
🥈 81 Silver

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "shape" from https://skillstore.io/skills/pbakaus-shape.md and its manifest at https://skillstore.io/api/skills/pbakaus-shape/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/pbakaus-shape.md Signed manifest GET /api/skills/pbakaus-shape/manifest Signed lockfile GET /api/skills/pbakaus-shape/lockfile

Test it

Using "shape". Plan a filter panel for a reporting dashboard.

Expected outcome:

  • Feature summary explaining who uses the panel and what decisions it supports.
  • Primary action focused on narrowing reports quickly without losing context.
  • Key states covering no filters, many filters, saved filters, errors, and mobile use.
  • Open questions about default filters, permissions, and export behavior.

Using "shape". Shape an onboarding checklist for a collaboration tool.

Expected outcome:

  • Design direction that feels calm, progress-oriented, and lightweight.
  • Layout strategy that emphasizes the next best action and completed milestones.
  • Interaction model for completing, skipping, and returning to checklist items.
  • Content requirements for labels, progress text, empty states, and success messages.

Using "shape". Create a brief for a mobile account security screen.

Expected outcome:

  • Primary user action focused on understanding account risk and taking one security step.
  • States for secure, warning, critical issue, loading, and failed verification cases.
  • Accessibility notes for clear status language, touch targets, and non-color indicators.

Security Audit

Safe
v4 • 7/6/2026 Open versioned report

The reported backtick pattern in SKILL.md is Markdown inline formatting around a file name, not shell execution. The skill is prompt-only and focuses on discovery questions and a design brief. No semantic security findings were identified.

1
Files scanned
96
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (1)
SKILL.md:72
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/pbakaus-shape/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/pbakaus-shape/security.svg)](https://skillstore.io/skills/pbakaus-shape?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/pbakaus-shape?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/pbakaus-shape/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/pbakaus-shape.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

pbakaus. (2026). shape security audit report (audit version 4) [Author version 2.1.1]. Skillstore. https://skillstore.io/skills/pbakaus-shape/audits/4

BibTeX citation

@techreport{pbakaus-pbakaus-shape-2026, author = {pbakaus}, title = {shape security audit report (audit version 4)}, institution = {Skillstore}, year = {2026}, number = {4}, url = {https://skillstore.io/skills/pbakaus-shape/audits/4}, note = {Author version 2.1.1} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "shape security audit report (audit version 4)" version: "2.1.1" type: report authors: - name: "pbakaus" date-released: "2026-07-06" url: "https://skillstore.io/skills/pbakaus-shape/audits/4" identifiers: - type: other value: "skillstore:pbakaus-shape:audit:4" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
100
Maintainability
87
Content
68
Community
100
Spec Compliance

What You Can Build

Shape a New Product Feature

Clarify audience, goals, edge cases, and success criteria before implementation begins.

Turn Ambiguous Requests Into Briefs

Convert a broad UI request into a practical design plan with states and interaction guidance.

Prepare a Design Handoff

Create a concise brief that aligns visual direction, layout strategy, content needs, and open questions.

Try These Prompts

Plan a Simple Feature 
Use shape to plan a profile settings page for a small team app. Ask discovery questions before creating the brief.
Define States and Content 
Use shape to plan a notification center. Focus on empty, loading, error, high-volume, and first-time states.
Prepare an Implementation Handoff 
Use shape to create a design brief for a billing dashboard. Include layout strategy, interactions, content requirements, and open questions.
Shape a Complex Redesign 
Use shape to plan a mobile-first redesign of a project overview page. Account for existing patterns, localization, performance, and accessibility.

Best Practices

  • Use the skill before implementation decisions are made.
  • Provide concrete user roles, data ranges, constraints, and examples when possible.
  • Review and confirm the brief before handing it to an implementation workflow.

Avoid

  • Do not ask it to write production code directly.
  • Do not skip discovery and request a finished layout immediately.
  • Do not use it without project design context when that context is required.

Frequently Asked Questions

What does this skill produce?
It produces a structured design brief for a feature before implementation starts.
Does it write code?
No. It plans UX and UI direction, then prepares guidance for later implementation.
When should I use it?
Use it during planning, before layout, component, and interaction decisions are locked.
What information should I provide?
Provide the feature goal, target users, constraints, data ranges, examples, and known anti-goals.
How does it use project design context?
It references existing /impeccable context and asks for setup when that context is missing.
Can I use it with Claude, Codex, and Claude Code?
Yes. The report lists support for Claude, Codex, and Claude Code.

Developer Details

Author

pbakaus

License

MIT

Author version

v2.1.1

Skillstore revision

r1

Repository

https://github.com/pbakaus/impeccable/tree/main/.agents/skills/shape/

Ref

e397ce5a135369cd6def89cb6400d013e2f68f2f

Maintenance freshness

7/18/2026

Usage

15 downloads · 65 views

File structure

📄 SKILL.md

More from pbakaus

View all

Related Skills

View all