Rinci App

iOS Swift Package

This repository is also a Swift Package named RinciApp. In Xcode, choose File → Add Package Dependencies, enter this repository URL, and select a version tag for production or a branch while developing.

import RinciApp

Use Tokens and TextStyles from the module. Sources/RinciApp/Resources/tokens.json is included as a package resource for tooling. Component and Page Specs are mirrored under Resources/specs/; use DesignSpecs.componentsIndexURL and DesignSpecs.pagesIndexURL when an app or an AI-assisted tool needs to discover them from the package. Custom font files are not generated by DHM; add and register licensed font files in the host app before using a custom font family.

This repository contains the design-token source maintained with DHM Tokens.

Repository contents

• tokens/tokens.json — DTCG token source for developers and AI-assisted tooling.
• DESIGN.md — design-system guidance, collections, modes, and naming conventions.
• .dhm/workspace.project.json — lossless plugin snapshot for designers who need to restore the workspace.

Page Specs

Page Specs are packaged under pages/. Use pages/index.json only to discover pages, then open pages/<page-slug>/page.json as the implementation entry. The entry is a developer/AI-ready, self-contained document with a readable node tree, normalized layout/appearance/typography data, token-path bindings, section references, and asset references. Use each node's sectionId and qualifiedPath when names repeat across sections; use layout.position.mode: absolute for manually positioned children; use geometry.type for non-rectangular shapes; and use appearance.effects[*].cssFilter together with the raw effect radius when reproducing Figma blur. Figma-only source IDs and scan fingerprints are intentionally kept out of this public projection; the lossless snapshot remains in .dhm/workspace.project.json.

Section files live in the page's sections/ folder for targeted implementation, and assets.json is the download-oriented asset manifest. For a full-page implementation, give the AI the page entry file first. For a focused correction, give it the relevant section file plus the page entry for context. Download the actual PNG/SVG files from Figma and place them at the asset paths before expecting image or icon pixels to match.

Workflow

1. Designers author and review tokens in DHM Tokens.
2. The plugin pushes the DTCG source and lossless snapshot to GitHub.
3. Developers and AI tools can consume the DTCG source directly.
4. Pull remote changes into the plugin before pushing again when the repository has changed outside the plugin.

Generated by DHM Tokens.