TypingMindTypingMindThe best frontend for AI
Front Comments logo

Front Comments

Community
Effeilo
front-comments

Add structured comments to a JS, TS, React (JSX/TSX), CSS, Sass, HTML, Vue, Svelte, or Astro file at level 1 (structure only) or full (level 1 + inline comments on every rule/method). Usage: /front-comments [full] [lang:fr]

Overview

PublisherEffeilo
Repositoryclaude-code-frontend-skills
Skill namefront-comments
Stars
3
Forks
0
Bundled files
12
Links
Skill sourceRepositoryHomepage
  • 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.

  • 12 bundled files

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

  • Open source

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

Installation

Install the Front Comments 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/Effeilo/claude-code-frontend-skills/tree/main/front-comments
  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/Effeilo/claude-code-frontend-skills.git /tmp/claude-code-frontend-skills
mkdir -p .claude/skills
cp -r /tmp/claude-code-frontend-skills/front-comments .claude/skills/front-comments
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Front Comments 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 Front Comments 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 Front Comments 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.

Comment the file that is currently open or explicitly mentioned by the user. Apply Level 1 comments by default, or Full (Level 1 + inline comments) if $ARGUMENTS contains full.

Detect the comment language from $ARGUMENTS:

  • If $ARGUMENTS contains lang:fr → write all comments in French
  • If $ARGUMENTS contains lang:es → write all comments in Spanish
  • If $ARGUMENTS contains lang:de → write all comments in German
  • Otherwise → write all comments in English (default)

Step 1: Handle existing comments

Before applying any rules, scan the file for existing comments:

  1. Read all existing comments and identify which ones contain non-obvious information, business rules, browser workarounds, ticket references, architectural decisions, "why" explanations. Ignore trivial comments that only restate the code (e.g. // increment counter).
  2. Remove all existing comments from the file, including trivial ones, misplaced ones, and well-written ones alike.
  3. Apply the structured commenting rules (Steps 2–3 below) to the now comment-free file.
  4. Reintegrate the semantic content of the valuable comments identified in step 1, fold their information into the appropriate new structured blocks (file header, JSDoc description, inline comment…) rather than reinserting them verbatim.

The goal: a clean, consistent structure where no useful information is lost.

Step 2: Detect the file language

Look at the extension of the target file:

  • If .js, .ts, .mjs, .jsx, .tsx → Read front-comments-js.md (located in the same directory as this skill file) and apply its instructions.
  • If .css, .sass, .scss → Read front-comments-css.md (located in the same directory as this skill file) and apply its instructions.
  • If .html → Read front-comments-html.md (located in the same directory as this skill file) and apply its instructions.
  • If .vue → Read front-comments-vue.md (located in the same directory as this skill file) and apply its instructions.
  • If .svelte → Read front-comments-svelte.md (located in the same directory as this skill file) and apply its instructions.
  • If .astro → Read front-comments-astro.md (located in the same directory as this skill file) and apply its instructions.

The path of this skill file is always available from context. Resolve the sub-file path relative to it.

Step 3: Apply the instructions from the sub-file

Follow every rule defined in the loaded sub-file for the requested level (Level 1 or Full).

Output rules (apply regardless of language)

  • Output the entire file with comments added, do not truncate.
  • Do not modify any existing code, only add comments.
  • Preserve all original formatting, indentation, and blank lines.
  • Write comments in the language detected from $ARGUMENTS (see above). Default: English.
  • For JS/TS files: use only /** */ style for JSDoc blocks and inline comments. Use // only for section dividers.
  • For CSS/SASS/SCSS files: use /* */ for section dividers and tertiary labels. Use /** */ for file headers, major section descriptions, and inline property group labels.

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 Front Comments AI skill do?

Add structured comments to a JS, TS, React (JSX/TSX), CSS, Sass, HTML, Vue, Svelte, or Astro file at level 1 (structure only) or full (level 1 + inline comments on every rule/method). Usage: /front-comments [full] [lang:fr]

Why use Front Comments on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Effeilo/claude-code-frontend-skills/tree/main/front-comments. 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 Front Comments?

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 Front Comments?

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

Is the Front Comments AI skill free?

It is published on GitHub by Effeilo. Check the repository for licensing terms. 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.

Related AI Skills

View all
openclaw logo

Solid

openclaw
OrganizationPopular

Write, port, review, or test Solid 2 UI in OpenClaw (Control UI, plugin views, Canvas hosts), including state ownership, Lit interop during the migration, native overlays, testing, performance, and…

82.4K
391.7K
9 files
View
openclaw logo

Canvas

openclaw
OrganizationPopular

Present hosted widget documents on a connected macOS panel and control panel visibility or navigation.

82.2K
391K
Instructions
View
openclaw logo

Diagram Maker

openclaw
OrganizationPopular

Create SVG/HTML or Excalidraw diagrams for concepts, architecture, flows, and whiteboards.

82.2K
391K
2 files
View
mattpocock logo

Grill With Docs

mattpocock
CommunityPopular

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

23K
273.1K
1 files
View

Set up your own AI workspace now

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