ワンクリックで
create-taginfo-project-file
Generate taginfo project JSON files for TILDA topics, extracting OSM tags from processing code.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Generate taginfo project JSON files for TILDA topics, extracting OSM tags from processing code.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Default FMC tech stack for geo-heavy React SPAs: Bun/Vite, React 19, TanStack, maps, styling, TypeScript editor/CLI alignment, tsconfig templates, browserslist client targets, Cursor MCP (Postgres, agent-browser), and when to pick sibling skills. Use when scaffolding a new app, evaluating libraries, setting up Bun install/global store or Knip, changing supported browsers or compat lint, setting up Cursor MCP, or making stack/architecture decisions on existing apps.
Download TILDA Geo dataset exports (GeoJSON, GPKG, FGB) from tilda-geo.de by bbox. Use when the user asks to export or download map data, bikelanes, roads, parkings, or other export tables for a bounding box.
Premium orchestrator (Fable 5, Sonnet 5, or GPT-5.6 Sol) with Composer 2.5 workers. Two separate setups: Cursor IDE (subagents in .cursor/agents) or Claude Code (cursor-agent CLI + .claude/skills). Use when configuring orchestration; pick the guide for your host.
FMC finish-work workflow: run bun run check, fix failures, commit with a user-facing English message by default, and only show a draft when the user clearly did not want a commit. Use for finish work, run checks, wrap up, land changes, or create commits.
E2E testing and browser automation for TanStack Start apps (FMC/TILDA). Use @playwright/test for committed suites/CI; agent-browser MCP (skill tech-stack) for agent exploration; this skill for smoke tests, stubbed auth, map hooks, and quick /tmp scripts. Not for Next.js.
React 19 + TypeScript for FMC TanStack Start apps: typed components, events, generics, ref-as-prop, Compiler-first memoization, and useEffect discipline (naming, when not to use Effect, alternatives). Use when typing React components/hooks/events, or writing/reviewing useEffect, useEffectEvent, derived state, data-fetch effects, or eslint-plugin-react-hooks effect rules. Not for routing/server boundaries (see tanstack-start-* skills).
SOC 職業分類に基づく
| name | create-taginfo-project-file |
| description | Generate taginfo project JSON files for TILDA topics, extracting OSM tags from processing code. |
Generate valid taginfo project files for TILDA topics by analyzing processing code to extract OSM tags.
Identify topic: Read processing/constants/topics.const.ts or ask user which topic to process
Read topic file: processing/topics/<topic>/<topic>.lua
*_todoList.lua) are ignored - they are for QA purposes and don't represent the main processing logicExtract OSM tags: See references/tag-extraction.md for detailed rules
:left, :right, :both variants - extract all usedCopyTags() with tags_cc are for data storage only, not filtering/processing logicCreate tag entries: For each tag, determine:
value (specific values only) or omit (all values)object_types from processing functions (see references/tag-extraction.md)description focusing on TILDA's use case, not general OSM docsGenerate JSON: Use assets/example.json as template
<topic> and <timestamp> placeholdersyyyymmddThhmmssZ (e.g., 20260123T143022Z)Save file: app/public/taginfo/tilda-<topic>.json (create directory if needed)
references/taginfo-schema.md)data_format, project.*, tags"node", "way", "relation", "area" onlyreferences/taginfo-schema.mdreferences/tag-extraction.mdassets/example.jsonprocessing/constants/topics.const.ts