Design PiscesOS apps and tools with the accepted PiscesOS UI, UX and icon style. Use when another app should feel consistent with PiscesOS, including coordinated Light/Dark themes, adaptive computer/tablet/phone layouts, components, layered icons and optional glass. Includes visual references, artwork and bundled UI/Icon/Figma workflows. It does not require redesigning the PiscesOS shell or adopting its launcher layout.
Instructions
---
name: piscesos-app-design
description: Design PiscesOS apps and tools with the accepted PiscesOS UI, UX and icon style. Use when another app should feel consistent with PiscesOS, including coordinated Light/Dark themes, adaptive computer/tablet/phone layouts, components, layered icons and optional glass. Includes visual references, artwork and bundled UI/Icon/Figma workflows. It does not require redesigning the PiscesOS shell or adopting its launcher layout.
metadata:
version: "1.0.0"
---
# PiscesOS App Design
Create apps that belong to the PiscesOS visual family while fitting their own tasks. This portable skill includes enough context for another Codex to work without the original conversation or computer. Read [App style and accepted decisions](references/app-style.md) first. Later explicit user instructions override this dated baseline.
## Route the task
| Work | Read |
| --- | --- |
| UI, UX, states, adaptive layout | [Integrated UI workflow](modules/ui-design/workflow.md) |
| App icons, artwork, material and exports | [Integrated Icon workflow](modules/icon-design/workflow.md) |
| App icon appearance editor | [Accepted editor behavior](references/icon-editor.md) |
| Match the existing visual family | [Visual examples](references/visual-examples.md), [Figma map and evidence](references/figma-map.md) and [saved design tokens](references/design-tokens.json) |
| Install, share or find files | [Package usage](references/package-usage.md) and [asset manifest](assets/manifest.json) |
The modules are included reference documents, not separate installed skills. Before a Figma action, follow the bundled Canvas/screen/component workflow and any enabled tool's mandatory skill prerequisites. A connected Figma account and file access remain necessary; the package includes no credentials.
## Design the app, preserve the family
Start with the app's purpose and existing functions. Choose navigation, information hierarchy, task flow and relevant states for that app. A notepad needs an editor, a file manager needs file navigation, and an administration tool needs readable forms/tables. **Do not impose the Desktop launcher grid, wallpaper, Start button or Server sidebar on every app.**
Reuse PiscesOS semantic color roles, typography, control states, restrained material and coordinated Light/Dark themes. The selected Apple community visual family and current official Apple HIG guide appearance; Material 3 supplements adaptation, behavior and accessibility. Do not label PiscesOS-specific tokens or gradient pairings as official Apple values. Support computer, tablet and phone where requested, preserving each host's native input and window behavior.
Give each app its own recognizable icon. Use included tool artwork as calibration, not as a requirement to copy another app's identity. The four-module PiscesOS logo and paired-rack Server logo remain product identities; do not substitute them for every app icon. Preserve accepted contours when refining existing artwork. Glass may be selective, and optical refraction is a separate opt-in effect.
Reuse current editable components/tokens when available. Inspect the actual relevant Figma frames rather than rebuilding a screenshot as a single bitmap. The saved token/preview files are attributed snapshots; inspect current styles before claiming exact parity. If access is unavailable, continue with an editable local prototype and accurately label it.
Review the requested scope in Light and Dark, including relevant loading, empty, error, focus, selection and success states. Check small-icon recognition, text contrast, keyboard/touch behavior, narrow windows and large text. Avoid ornamental detail that competes with the task. New deliverables use English unless requested otherwise; preserve existing localization.
Retain SVG and other original uploaded artwork; use cached PNG for normal icon display and appropriate host exports. Deliver editable work, previews and requested exports, stating whether it is a design, implementation or deployment. Preserve functions, runtimes, authentication, data ownership, updates and package identities unless the current task explicitly changes them. A design request alone does not publish or install software.
