← All skills

Native context · Workhuman AI practice

Native has its own rules

I developed a separate native context workflow so agents consult the right sources and preserve decisions about the app and its library.

rcs-native-design
Native design · Structures that adapt to their content.
Native design · Structures that adapt to their content. Conceptual illustration created with AI.

The problem

Why this belongs
in the workflow.

A narrow web screen and a native app can share a topic while needing different components, platform behaviours and accessibility semantics.

What the skill makes explicit.

01

Choose native or responsive-web context from the destination, not from the word “mobile”.

02

Resolve component identity and available platform modes before using an instance.

03

Separate product styling from operating-system chrome and record unresolved limitations.

Evidence and learning

From instructions
to practice.

A dated button decision records how inspection overturned the assumption that height already followed content. I extended the change and accepted a loading-state height difference.

Contribution and evidence scope

The recorded library changes were made in the source Figma file and were not published at that point.

Source: the supplied rcs-native-design skill and associated records. Internal component identifiers and company endpoints are omitted.

Process flow

How this skill handles a task.

A narrow web screen and a native app can share a topic while needing different components, platform behaviours and accessibility semantics.

  1. 01

    Identify platform

    Separate native app work from responsive web.

  2. 02

    Inspect component

    Resolve component identity, variants and platform modes.

  3. 03

    Apply native rules

    Keep product typography separate from OS chrome.

  4. 04

    Record decision

    Preserve the decision and unresolved limitations.

DECISION CHECKPOINT

Is this a native destination?

Proceed

Apply the native registry and platform rules.

Alternative / follow-up

Route responsive web work to rcs-design.

Editorial map of the documented instructions, not a recorded execution.

Inside the skill

Instructions you can inspect.

Source excerpt from rcs-native-design/SKILL.md, lines 18 to 29. The same text is available directly below.

1. Read Bruno's own context first

In this order:

• [internal path removed] — how he works (stable)

• [internal path removed] — dated log of specific corrections (append-only)

If either is missing, continue and say so in the reply.

This layer comes first on purpose: an explicit correction from Bruno beats any documentation, including Terra's and including this gate. When decisions.md contradicts preferences.md, the more recent decisions.md entry wins.