X Page logo

X Page

Community
roslove44
x-page

Creates the X / Twitter profile visuals (profile photo and header / banner) at X's official dimensions. Use when the user wants an "X/Twitter profile photo", a "Twitter header", an "X banner" or "the X avatar" for a project. Produces one or two .tsx templates at the sizes X imposes (profile 400x400, header 1500x500), aligned with the brand guidelines, rendered as PNGs through the project's engine. Requires a project with its brand.md in place.

Overview

Publisherroslove44
Repositorybrand-artisan
Skill namex-page
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 X Page 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/x-page
  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/x-page .claude/skills/x-page
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable X Page 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 X Page 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 X Page 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.

x-page: X / Twitter profile visuals

Goal: produce the PNG assets of an X (Twitter) profile at the official dimensions (source: X help, "customize your profile"), aligned with the guidelines. Two possible visuals, independent of each other:

  • profile photo: the brand, 400×400, cropped to a circle;
  • header / banner: 1500×500 (3:1).

This is a specialization of new-template with the X constraints hard-coded. Same conventions: the Template contract, assets through brand(), fonts discovered in fonts/, export default ... satisfies Template.

0. Prerequisites (blocking)

The chain project -> template folder -> guidelines must exist:

  • Resolve <project> (from the arguments, otherwise ask).
  • Check templates/<project>/ and brands/<project>/brand.md.
  • Missing guidelines or project -> STOP: ask for /new-project <project> first. No visual without guidelines (CLAUDE.md rule).

1. Frame it

  • Which visual(s)? Ask: profile, header, or both.
  • Default slugs: x-profile (400×400), x-header (1500×500). Check that the target .tsx does not exist.
  • Read brands/<project>/brand.md: palette, type, the logo / favicon variants and their rules depending on the background, and the don'ts.
  • If the project already holds a .tsx, read it as a style reference.

2. X constraints (to respect)

VisualSizeRatioNotes
Profile photo400×4001:1cropped to a circle
Header / banner1500×5003:1cropped on mobile (the edges)
  • Format: PNG or JPG. Opaque background. X documents no maximum weight for these two visuals (the official 5 MB applies to tweet images).
  • Profile: square, brand centered, nothing important in the corners (displayed as a circle). 400×400 is the official size; scale: 2 is advised for crispness. For an organization, prefer the mark alone / the favicon over the wordmark, which is illegible when small. Follow brand.md.
  • Header (1500×500): on mobile, X crops the sides, so keep the important content centered, with comfortable side margins.
  • Dead zone bottom left (profile photo): on the profile page, the avatar covers the bottom left of the header, so any text or logo falling there is hidden. Leave it clear: left margin ~2.5 % of the width, box ~23 % W × ~35 % H anchored bottom left. On 1500×500: roughly x 38→388, y 325→500.

3. Write the template(s)

templates/<project>/<slug>.tsx, with colors as constants taken from the guidelines (invent nothing). Pick SIZE according to the visual:

tsx
import type { ReactNode } from "react";
import { brand, type Template } from "brand-artisan";
// import { readFile } from "node:fs/promises"; // if you load the mark

// Pick according to the visual:
const SIZE = { width: 400, height: 400 };   // Profile 1:1 (scale:2 advised)
// const SIZE = { width: 1500, height: 500 };  // Header 3:1

// <Project> guideline palette (from brands/<project>/brand.md).
const INK = "#......";

function render(): ReactNode {
	return (
		<div style={{ width: "100%", height: "100%", display: "flex", /* ... */ backgroundColor: INK }}>
			{/* brand centered (profile) OR lockup + standfirst centered (header) */}
		</div>
	);
}

export default { size: SIZE, title: "<Human title>", render } satisfies Template;

Shared conventions: assets through brand("<project>/..."), fonts discovered in fonts/; a missing font -> the "missing font" appendix in new-template, never silently.

4. Verify

  • npm run typecheck -> green.
  • npm run build -> writes out/<project>/<slug>.png.
  • Check each PNG: exact dimensions (400×400 / 1500×500), opaque background.
  • Profile: check the circular crop (nothing in the corners).
  • Header: nothing important in the bottom-left corner (profile photo) nor too close to the side edges (mobile crop).
  • Preview: npm run dev then /<project>/<slug>.

Success criterion: PNGs at X's exact dimensions, opaque, brand centered and legible for the profile, safe area respected for the header, and using only colors and type from brand.md.

Frequently asked questions

What does the X Page AI skill do?

Creates the X / Twitter profile visuals (profile photo and header / banner) at X's official dimensions. Use when the user wants an "X/Twitter profile photo", a "Twitter header", an "X banner" or "the X avatar" for a project. Produces one or two .tsx templates at the sizes X imposes (profile 400x400, header 1500x500), aligned with the brand guidelines, rendered as PNGs through the project's engine. Requires a project with its brand.md in place.

Why use X Page on TypingMind?

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

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

Which AI models can use X Page?

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 X Page?

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

Is the X Page 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 👇