New Project logo

New Project

Community
roslove44
new-project

Initializes a new BrandArtisan visuals project by laying down its reference guidelines. Use when the user wants to create/add a new project, start a new brand or a new visual identity ("new project", "add project X", "set up brand Y"). Creates brands/<project>/brand.md (mandatory before any visual) and the templates/<project>/ folder.

Overview

Publisherroslove44
Repositorybrand-artisan
Skill namenew-project
Stars
5
Forks
0
Bundled files
Instructions only
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.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

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

Installation

Install the New Project 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/roslove44/brand-artisan/tree/main/skills/new-project
  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/roslove44/brand-artisan.git /tmp/brand-artisan
mkdir -p .claude/skills
cp -r /tmp/brand-artisan/skills/new-project .claude/skills/new-project
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable New Project 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 New Project 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 New Project 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.

new-project: bootstrapping a visuals project

Goal: lay down the two references of a new project in brands/<project>/: brand.md (visual identity, blocking: no visual without it) and project.md (substance and voice, for writing the text). A CLAUDE.md rule.

1. Determine the <project> slug

Take it from the arguments. Otherwise ask. It is a kebab-case slug (e.g. calame, my-app). Check that it does not already exist: brands/<project>/ or templates/<project>/. If it does -> stop, say so.

2. Collect the guidelines (invent nothing)

Interview the user. Never invent colors, type or logo: that is the heart of the project rule. Collect at least:

  • Concept / meaning of the logo and the name.
  • Typography: typeface, weight, source. Note: the available families and weights are those present in fonts/, discovered automatically by the engine. If the guidelines require another font absent from fonts/, follow the Missing font procedure below: offer to pre-install it now, or let /new-template fetch it for the first visual that needs it.
  • Palette: for each role, the hex (+ Tailwind landmark if known) and the usage.
  • Logo / favicon variants available and when to use them.
  • Usage rules and don'ts.

Collect the substance too (for project.md): a one-sentence pitch, what the product does, audience and language, value proposition, editorial voice (register, how it addresses the reader), vocabulary (exact name, URL) and forbidden claims (don't invent figures).

If the user does not have everything yet, write down what is known and mark the gaps with _(to be defined)_ rather than filling them at random.

3. Write brands/<project>/brand.md

Mirror the structure of brands/calame/brand.md (that is the reference):

  1. Title # Brand guidelines: <Project> + a short intro.
  2. ## 1. Concept and meaning (with Typography and Colors subsections).
  3. ## 2. Variants (logotype, favicon/icons) if applicable.
  4. ## 3. Usage rules (clear space, minimum size, backgrounds, Don't).
  5. ## 4. Regeneration only if some assets are generated by a script.

The logo and favicon files live next to it, in brands/<project>/logo/ and brands/<project>/favicon/. Don't create fake assets: if the user has files, tell them where to drop them. If the assets are to be generated by a script (like Calame's), that is the brand-assets skill's job.

3b. Write brands/<project>/project.md

Mirror the structure of brands/calame/project.md (that is the reference):

  1. # Project: <Project> + a short intro (what the file is for).
  2. ## 1. In one sentence (the pitch).
  3. ## 2. The product (what it does, the differentiator).
  4. ## 3. Audience (personas, market, language).
  5. ## 4. Value proposition (benefits, by priority).
  6. ## 5. Editorial voice (register, how it addresses the reader, format, do/don't).
  7. ## 6. Vocabulary & claims (exact name, URL, approved lines, forbidden claims: no invented figures).

Same rules as for brand.md: invent nothing, mark the gaps with _(to be defined)_ or _(to be confirmed)_.

4. Create the templates tree

Create the templates/<project>/ folder (it will hold the .tsx files).

5. Wrap up

Recap what was created and what is still _(to be defined)_ in the guidelines. Point to what comes next: /new-template <project> <name> for the first visual.

Success criterion: brands/<project>/brand.md and brands/<project>/project.md exist, follow the reference structure, and contain no invented color, type or claim (gaps marked _(to be defined)_).

Missing font (procedure)

If the guidelines require a font that is not in fonts/:

  1. Ask for permission to fetch it: this is an outbound network action, never silent. Name the source and the license before downloading.
  2. Trustworthy source, ttf/otf format (Satori does not read woff2): the raw .ttf from the official repo (github.com/google/fonts) or an @fontsource/<font> package. Most Google Fonts are OFL/Apache -> fine. A proprietary font or an ambiguous license -> refuse and ask the user to provide the file themselves.
  3. Download to fonts/<Family>-<weight>.ttf, using curl -L <url> -o ... or Invoke-WebRequest -OutFile. WebFetch is not suitable (binary). The file name is authoritative: it determines the family the templates cite, in PascalCase (GeistMono-600.ttf -> Geist Mono, 600).
  4. Check the file: non-zero size and a real font header (.ttf starts with 00 01 00 00, OpenType with OTTO), not an HTML error page in disguise.
  5. Document the license: drop its text into fonts/ and add the matching row to the table in fonts/NOTICE.md. No code declaration: the engine discovers the file at startup, provided its name follows the <Family>-<weight>.ttf convention from step 3.
  6. Confirm before committing the .ttf (a binary) with the user.

If the user refuses -> do not pre-install; note in the guidelines that the font is _(to be provided)_ and let /new-template ask the question again.

Frequently asked questions

What does the New Project AI skill do?

Initializes a new BrandArtisan visuals project by laying down its reference guidelines. Use when the user wants to create/add a new project, start a new brand or a new visual identity ("new project", "add project X", "set up brand Y"). Creates brands/<project>/brand.md (mandatory before any visual) and the templates/<project>/ folder.

Why use New Project on TypingMind?

Because you install it once and use it with any model. New Project 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 New Project in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/roslove44/brand-artisan/tree/main/skills/new-project. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use New Project?

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 New Project?

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

Is the New Project AI skill free?

Yes. It is published on GitHub by roslove44 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 👇