agentleFS
clideyclidey/whodb/.agents/skills/new-frontend-page/SKILL.md

new-frontend-page

Skill5.1k starsChanged 3 days agoApache-2.0View on GitHub

Add a new page/route to the WhoDB frontend with proper localization and routing

Trending

Less talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 3 mentionsMar 2026: 8 mentionsApr 2026: 4 mentionsMay 2026: 5 mentionsJun 2026: 6 mentionsJul 2026: 5 mentionsAug 2026: 6 mentionsSep 2026: 6 mentionsOct 2026: 9 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the clidey/whodb repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about clidey/whodb

The biggest 5 of 60 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 60

Talked about on GitHub, Bluesky and Hacker News (60 times).

On GitHub · 50

45 more on GitHub

On Bluesky · 7

2 more on Bluesky

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not add or update non-English locale entries unless the user explicitly asks for translation.

    line 37
  2. Distinctive:

    Update the sidebar configuration to include the new page with appropriate icon and label.

    line 44
  3. Very specific:

    Add test file frontend/e2e/tests/features/<feature-name>.spec.mjs following existing patterns.

    line 62

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Add a New Frontend Page

Steps

1. Create Page Component

frontend/src/pages/<feature-name>/index.tsx
import { FC } from 'react';
import { useTranslation } from '@/hooks/use-translation';

export const FeatureNamePage: FC = () => {
  const { t } = useTranslation('pages/feature-name');

  return (
    <div>
      <h1>{t('title')}</h1>
    </div>
  );
};

2. Add Translation File

Create frontend/src/locales/pages/<feature-name>.yaml:

en_US:
  title: Feature Name

Do not add or update non-English locale entries unless the user explicitly asks for translation.

3. Add Route

In the router configuration, add the new route. Follow existing patterns for layout and navigation guards.

4. Add Sidebar Entry (if needed)

Update the sidebar configuration to include the new page with appropriate icon and label.

5. Add Keyboard Shortcut (if needed)

In frontend/src/utils/shortcuts.ts:

export const SHORTCUTS = {
  // ...existing
  featureName: { key: 'X', modifiers: ['meta'], displayKeys: ['⌘', 'X'] },
};

6. Verification

cd frontend && pnpm run build:ce
cd frontend && pnpm start  # Visual verification in browser

7. E2E Test

Add test file frontend/e2e/tests/features/<feature-name>.spec.mjs following existing patterns.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.