Humane Functionalism logo

Humane Functionalism

Community
kemiljk
humane-functionalism

Improve UI and UX through Danish functionalism. Use for a Danish functionalist design pass on a screen or flow, grounding hierarchy, interaction, human fit, and craft in actual use.

Overview

Publisherkemiljk
Repositoryskills
Skill namehumane-functionalism
Stars
64
Forks
3
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by kemiljk on GitHub. Read the source before you install it.

Installation

Install the Humane Functionalism AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/kemiljk/skills/tree/main/skills/humane-functionalism
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/kemiljk/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/humane-functionalism .claude/skills/humane-functionalism
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Humane Functionalism in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Humane Functionalism on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Humane Functionalism is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Humane Functionalism

Apply Danish functionalism to the way an interface is organised, used, and experienced. Let human needs, context, construction, and perception guide its form.

The foundation is Danish architectural and product functionalism, with relevant lessons from Danish Modern furniture. These are contemporary UI applications, not a historical manifesto or rules those designers wrote for software. Read research and sources when explaining an attribution or exploring a particular designer's contribution. The working guidance below is self-contained.

Start from use

Infer the primary task, audience, frequency, input methods, platform, and constraints from the request and available design or code. State the intended improvement briefly. Ask only when a missing decision would materially change the work.

Inspect the named screen or flow, existing tokens and components, realistic content, and relevant states. A screenshot supports visual observations; source supports implementation observations; neither proves task success. Distinguish observed friction from a hypothesis that needs testing.

Review requests produce findings. Requests to improve, redesign, or implement authorize scoped changes. Preserve product requirements, brand identity, useful density, and working conventions. Fit this lens to the requested task rather than expanding a local correction into a complete redesign.

Design through the Danish references

These connections are an editorial synthesis. Use the relevant lenses to make decisions; do not force a finding or an edit for every designer.

Human fit — Kaare Klint

Klint's studies of proportions and existing furniture suggest a method: examine use before choosing form.

Size and arrange controls around reading, reach, dexterity, and the input method. Test real content, long labels, text scaling, and varied abilities. Preserve recognisable controls and useful shortcuts while correcting their weaknesses. A single assumed average user is insufficient.

Check: can the intended task be completed with the relevant inputs and content variations without clipping, precision targeting, or hidden essential actions?

A coherent whole — Arne Jacobsen

Jacobsen's integration of architecture and interiors suggests treating the flow and its details as one designed experience.

Connect navigation, terminology, hierarchy, components, and feedback. Use the same language and state meanings from entry through completion. Check the relationship between screens before polishing an isolated component. Coherence does not require replacing platform conventions with bespoke controls.

Check: follow one task across screens; do labels, action priorities, focus, and state transitions remain intelligible?

Perceptual comfort — Poul Henningsen

Henningsen's work on directing light and controlling glare makes the experienced effect a useful starting point.

Give attention a clear destination through type, spacing, grouping, and selective emphasis. Reduce competing accents and unnecessary motion. Preserve readable contrast and visible focus; a quieter screen must still communicate. Choose colour for content, identity, and conditions of use rather than a prescribed Scandinavian palette.

Check: can people distinguish content, actions, status, and focus at the intended viewing size? Physical glare and screen contrast are different phenomena; this is a perceptual analogy, not a lighting formula for UI.

Organisation from activity — Vilhelm Lauritzen

Lauritzen's arrangement of buildings around their functions suggests deriving information architecture from the activities it must support.

Map the user's sequence and the decisions at each step. Place controls and information where they are needed. Separate incompatible activities; keep related ones connected. Expose location, next actions, and routes back. Include interruption, errors, and recovery in the flow.

Check: walk from entry to completion and through a failure. Can the user understand what happened and continue without losing work?

Everyday usefulness — Børge Mogensen

Mogensen's work for ordinary living and production suggests investing quality in repeated, practical use.

Prioritise frequent and consequential tasks. Make defaults useful, common actions discoverable, and recovery forgiving. Support modest devices, slow connections, keyboard navigation, and assistive technology. Keep essential tasks usable without optional media or effects. Low feature count is not inherently more useful.

Check: repeat the common task under a relevant constraint. Does the interface still work comfortably without extra setup or avoidable waiting?

Fit to context — Kay Fisker

Fisker's functional tradition suggests adapting useful conventions and materials to their setting.

Work with the product's existing system, platform, audience, and content. Set density and layout by the work: an expert comparison table may need many visible values; a touch form may need generous spacing. Improve proven patterns before replacing them. A visual style alone cannot establish fitness for use.

Check: does the proposed change solve a local problem, and what useful knowledge or capability would the change displace?

Construction as craft — Hans J. Wegner and Poul Kjærholm

Their related Danish Modern work offers specific lessons in comfort, joinery, structure, and material properties.

Treat semantics, responsive layout, component boundaries, and state transitions as the construction of the interface. Use the platform's strengths. Repair the responsible component and check its other uses. Make loading, saved, failed, and disabled states correspond to actual behaviour. Review the points where components meet as carefully as their resting appearance.

Check: exercise long content, resizing, focus movement, and a failed operation. Does the construction support what the visual design promises?

Resolve tensions through use

TensionDecision rule
Simplicity versus discoveryKeep labels, boundaries, and persistent essential actions when they help people act. A disappearing field is not an improvement.
Calm versus densityPreserve information needed for comparison. Improve alignment and grouping before moving useful content behind extra clicks.
Coherence versus contextShare meanings and patterns; allow layout and density to vary with the task and device.
Restraint versus expressionRetain colour, character, and expressive form when they support meaning, identity, comfort, or pleasure. Finn Juhl is a related Danish Modern counterpoint to strict functionalist form, not evidence for a universal style.
Speed versus considered actionRemove redundant steps; retain review where it prevents a costly mistake. Click count alone is not task quality.

Make and verify the improvement

For each material issue, connect observed condition → user consequence → smallest effective change → verification. For example: a saved indicator appears before the request completes → users may leave with unsaved work → distinguish saving, saved, and failed states → exercise a failed save and retry without losing input.

Prioritise task completion, accessibility, and dependable feedback; then comprehension and recovery; then visual refinement. Use existing system values where they fit. Revise tokens when the problem is systematic.

Revisit the affected task with representative content, a contrasting layout size, and relevant input methods. Exercise changed loading, success, failure, and recovery states. Check visible focus, readable contrast, text scaling, and reduced motion where the change touches them; use current platform guidance for numerical requirements.

Match evidence to the claim: visual comparison for hierarchy, an input sequence for operation, failure simulation for recovery, and network or runtime measurements for performance. If a check is unavailable, say what remains unverified. Do not infer accessibility from appearance or invent usability results.

Deliver the requested design, code, or review with the consequential changes, strengths preserved, checks performed, and remaining limits. Stop when further changes no longer improve the task or experience.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Humane Functionalism AI skill do?

Improve UI and UX through Danish functionalism. Use for a Danish functionalist design pass on a screen or flow, grounding hierarchy, interaction, human fit, and craft in actual use.

Why use Humane Functionalism on TypingMind?

Because you install it once and use it with any model. Humane Functionalism is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Humane Functionalism in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/kemiljk/skills/tree/main/skills/humane-functionalism. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Humane Functionalism?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Humane Functionalism?

As many as you like. As long as a model supports skills, you can use Humane Functionalism with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Humane Functionalism AI skill free?

Yes. It is published on GitHub by kemiljk under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇