· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →The Freak Company v0.1.13
Native Apple apps with FreakUI
From the developer
Not specified in the available declarations: capabilities, limitations, pricing & account requirements.
Create a native app for iPhone, iPad, and Mac with FreakUI.
Developer declarations; not independently tested. Listing last checked Nov 20, 2026. Package observed Nov 19, 2026.
From the marketplace listing
Build a single-target, multi-platform native Swift application for iPhone, iPad, and macOS from one prompt. FreakUI establishes a robust clean architecture foundation with dependency injection, programmatic navigation, MVVM, and platform-specific root views. Its custom theme initialization, precision-focused components, utilities, and extensions give the interface a distinct and consistent identity. Beyond project creation, dedicated FreakUI skills help shape interface sections, add components, and evolve the interface as the app grows.
Language: English · Automatically detected from descriptions.
Exact text from the indicated source. A mention alone does not establish support for your task.
FreakUI
Native Apple apps with FreakUI
Build a single-target, multi-platform native Swift application for iPhone, iPad, and macOS from one prompt. FreakUI establishes a robust clean architecture foundation with dependency injection, programmatic navigation, MVVM, and platform-specific root views. Its custom theme initialization, precision-focused components, utilities, and extensions give the interface a distinct and consistent identity. Beyond project creation, dedicated FreakUI skills help shape interface sections, add components, and evolve the interface as the app grows.
· 1 observation
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →--- name: add-component description: Add or replace a focused SwiftUI control, content block, row, chart, feedback state, layout, or navigation surface with FreakUI. Use in an existing FreakUI project; use build-dashboard for a whole dashboard and create-app for a new project. --- # Add a FreakUI component Make one focused interface improvement with the current FreakUI public API. This skill works locally and does not call the FreakUI generation service. Read [component-map.md](references/component-map.md) to choose the component family, then inspect the exact API in the project's installed FreakUI version before editing. ## Workflow 1. Read the active workspace instructions and inspect the target view, its state and actions, the current theme, supported platforms, and the project's FreakUI dependency version. 2. Confirm the intended behavior and visual role when they are not already clear. Preserve existing product logic; a component replacement must not silently change validation, persistence, navigation, or destructive-action behavior. 3. Choose the narrowest FreakUI component or utility that satisfies the intent. Prefer composition of existing public types over a new wrapper that duplicates FreakUI behavior. 4. Inspect the installed source, Swift interface, or Xcode Quick Help for the exact initializer and supporting types. Do not guess an API from a component name or from another FreakUI version. 5. Implement with the project's existing data flow and use FreakUI theme tokens, component sizes, sizing modes, surface appearances, interactions, and formatters where they fit. 6. Check all supported platforms affected by the edit. Preserve accessibility labels, Dynamic Type, focus, keyboard input, loading, empty, error, and disabled states that apply to the component. 7. Run only verification authorized by the active workspace and report skipped build checks truthfully. ## Boundaries - Do not add unrelated screens, models, services, or dependencies. - Do not restyle the entire app when the user asked for one component. - Do not replace a native SwiftUI primitive when FreakUI does not provide a better semantic fit. - Do not copy product-specific implementation from another app; use public FreakUI contracts and the target project's own models. ## Handoff Report the component selected, the user-visible improvement, exact files changed, and verification performed. Keep internal API exploration and command output out of the final response unless it explains a blocker.
Referenced files: 3 — file references are metadata, not package contents.
--- name: build-dashboard description: Design and implement a distinctive, adaptive SwiftUI dashboard with FreakUI charts and data-display components. Use for overview, metrics, progress, balance, nutrition, finance, or workout dashboards in an existing FreakUI project. --- # Build a FreakUI dashboard Turn real product data and actions into one clear dashboard hierarchy. This skill works locally in an existing project and does not call the FreakUI generation service. Read [dashboard-system.md](references/dashboard-system.md) before proposing or implementing the dashboard. ## Workflow 1. Read the active workspace instructions, then inspect the project's architecture, current dashboard or destination screen, data model, state flow, navigation, theme, supported platforms, and installed FreakUI version. 2. Determine whether the user wants a layout proposal or implementation. For a proposal, provide the hierarchy and component choices without editing. For implementation, preserve the project's existing architecture and authorization boundaries. 3. Identify the smallest useful information hierarchy: summary, progress, trend, breakdown, recent activity, and primary action. Include only sections supported by real data or explicitly requested placeholders. 4. Map each section to the narrowest FreakUI component in the reference. Inspect the exact public API in the installed FreakUI source or Xcode interface before coding; do not guess initializers or copy product-specific code from another app. 5. Build one semantic dashboard that adapts across the project's supported platforms. Prefer shared data and section composition with deliberate layout adaptation over duplicated product logic. 6. Keep formatting, aggregation, loading, empty, and error behavior explicit. Preserve accessibility labels, Dynamic Type, keyboard behavior, and the project's existing interaction model. 7. Run only verification authorized by the active workspace. Never claim a platform build succeeded when it was skipped or failed. ## Quality bar - Establish one dominant summary before secondary metrics. - Use charts only when they reveal a comparison, distribution, progress, or trend more clearly than text. - Use FreakUI theme colors, typography, spacing, radius, component sizes, and surface appearances instead of recreating a parallel design system. - Avoid a uniform card grid. Vary hierarchy through component role, size, span, and composition while keeping a coherent rhythm. - Keep business rules and data mutations outside presentation views. ## Handoff Report the dashboard structure, exact files changed, supported platform behavior, and verification performed. Keep technical output concise and name one concrete remaining action when verification is incomplete.
Referenced files: 3 — file references are metadata, not package contents.
--- name: create-app description: Create a clean, single-target native app for iPhone, iPad, Mac, or all three with FreakUI. Use for a new FreakUI project; do not use to modify an existing project or continue general app development. --- # Create a FreakUI app Create one new Xcode project and leave it useful on its first run. FreakUI returns a verified foundation blueprint. Destination inspection, font-file handling, source writing, optional example content, package resolution, and compilation stay on the user's Mac. Use plain product language with the user: say **app**, **project**, **generation access**, and **verification**. Reserve **contract**, **blueprint envelope**, **recipe**, and schema field names for tool calls and diagnostics. Read [contract-1.md](references/contract-1.md) before gathering the request. Read [fonts.md](references/fonts.md) only when the user supplies font files. Read [local-validation.md](references/local-validation.md) before writing or validating the returned blueprint. ## Required generation boundary `FreakUI.create_app_blueprint` is the only authorized source of a new FreakUI project foundation. Before intake, destination inspection, or any filesystem change, confirm that this tool is exposed in the current task. If it is unavailable, stop without creating or modifying files and report: **Could not complete: the FreakUI generation connection is unavailable in this task. Reconnect FreakUI and start a new task.** Never synthesize or copy a replacement foundation from a local FreakUI checkout, another app, a cached blueprint, examples, templates, or prior generated source. Never substitute the `build-dashboard` or `add-component` workflow for `create-app`. Tool unavailability is a blocking failure, not permission to approximate generation locally. ## Conversation - Start with the product, not a configuration inventory. Ask what the app does, which Apple devices it should support, its main sections, and how it should feel. If the user asks what choices are available, say: “Tell me what the app does, which Apple devices it should support, and its main sections. If you have a visual preference, describe the mood, how compact or spacious it should feel, and whether corners should be sharp or rounded. I can propose sensible defaults for everything else.” - Describe interface density naturally as compact, balanced, or spacious. Describe corners naturally as sharp, subtly rounded, or soft and rounded. Keep density, corner character, and overall mood as independent choices. - Infer safe defaults when the user has no preference. Use Apple System for text, Apple System Monospaced for numbers, and include realistic example content so the first run is not a collection of empty screens. - Do not ask about third-party notices unless the user supplies or requests external fonts, assets, or licensed material. Use no notices otherwise. - Gather missing information in one grouped question when practical. Translate the answer into the supported request and propose close supported screen icons without exposing the symbol catalog. - Settings is built into every generated foundation and is not an app-specific top-level screen. If the user includes Settings among the main sections, preserve that intent by omitting it from `topLevelScreens`, confirming `Settings: Included` separately, and keeping two to five other app-specific sections. Ask for another app-specific section only when removing Settings would leave fewer than two. - Show one concise confirmation with the app name, bundle identifier, devices, ordered sections, appearance, accent color, example-content choice, and destination. Show fonts only when they are custom and notices only when they exist. Confirmation authorizes creating the project, adding the agreed example content locally, resolving packages, and compiling the selected platform families. Do not generate until the user confirms. - If the user changes a choice, acknowledge the change and conf
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 9 — file references are metadata, not package contents.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 19, 2026.
plugin_asdk_app_6a90427764b8819187cb80f14e808fa9
Download plugin data (JSON)Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.