[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PDGZJ7NBHZ93SQYGSND5YM":3,"skill-same:01M6PDGZJ7NBHZ93SQYGSND5YM":90},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":64,"repositoryHtmlUrl":65,"repositoryHomepageUrl":65,"ownerHtmlUrl":66,"ownerBlogUrl":67,"ownerDescription":68,"updatedAt":69,"install":70,"resources":83},"01M6PDGZJ7NBHZ93SQYGSND5YM","design-md-to-shadcn",null,"Applies an external DESIGN.md (Google Labs design-token format) to a project's shadcn\u002Fui theme. Activate when the user provides or references a DESIGN.md \u002F design.md file, a designmd.app or Stitch design system, a downloaded brand design system, or asks to 'apply a design system \u002F theme' to a shadcn project. Translates DESIGN.md tokens into shadcn CSS variables in the project's theme CSS file and turns the prose into component guidance. Inbound-only: does not extract a DESIGN.md from the project.","douinc\u002Fagent-skills","douinc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F104253814?v=4","01M6PDGX2D777TNA7NETDKDHCW","dou inc.","01M6PDGX6QMFW72GNMX59GKN6P",1,"MIT","https:\u002F\u002Fgithub.com\u002Fdouinc\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdesign-md-to-shadcn\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"design md to shadcn","shadcn","design md","design","references","Variables","theme","css variables","app","token","project","stitch","activate","only","brand","ui","design system","component","css","google","2026-11-10 10:12:30",false,"---\nname: design-md-to-shadcn\ndescription: \"Applies an external DESIGN.md (Google Labs design-token format) to a project's shadcn\u002Fui theme. Activate when the user provides or references a DESIGN.md \u002F design.md file, a designmd.app or Stitch design system, a downloaded brand design system, or asks to 'apply a design system \u002F theme' to a shadcn project. Translates DESIGN.md tokens into shadcn CSS variables in the project's theme CSS file and turns the prose into component guidance. Inbound-only: does not extract a DESIGN.md from the project.\"\nmetadata:\n  author: initred\n  email: initred@dou.so\n  version: \"1.0.0\"\n---\n\n# DESIGN.md → shadcn\u002Fui\n\nTake an external **DESIGN.md** (the Google Labs design-token format, version `alpha`, Apache-2.0) and apply it to the project's shadcn\u002Fui theme.\n\n## What this skill is for\n\nThe DESIGN.md format pairs machine-readable YAML front matter (design tokens) with markdown prose (rationale + guidance). It uses a **Material-3-style token namespace** (`primary`, `secondary`, `tertiary`, `neutral`, `surface`, `on-surface`, `surface-container-*`, `on-primary`, …) that does **not** map 1:1 to shadcn's fixed semantic tokens.\n\nThe official `design.md export --format css-tailwind` emits `--color-primary` etc. — single-mode, no foreground pairs — which is **not** usable by shadcn. This skill provides the missing mapping layer: DESIGN.md tokens → shadcn `:root` \u002F `.dark` CSS variables, plus prose → component guidance.\n\n- **Direction:** inbound only (external DESIGN.md → the project). Do not generate a DESIGN.md from the project.\n- **Dependencies:** none. No `@google\u002Fdesign.md` CLI, no package installs. Pure parsing + the mapping table in [rules\u002Ftoken-mapping.md](rules\u002Ftoken-mapping.md).\n\n## Project target (locate, then verify before editing)\n\nFirst find the project's shadcn theme CSS file and config — don't assume a path:\n\n- **Theme CSS file:** the file holding shadcn tokens as CSS variables in `:root` (light) and `.dark`. Common locations: `app\u002Fglobals.css`, `src\u002Findex.css`, `src\u002Fapp.css`, `resources\u002Fcss\u002Fapp.css`, `styles\u002Fglobals.css`. Confirm by grepping for `--background`, `--primary`, or `--radius`.\n- **`components.json`** (repo root): read `style`, `baseColor`, `cssVariables`, `tailwind.css` (points to the theme file), and the `aliases`. Note whether tokens are HSL\u002F`oklch()`\u002Fraw and match that convention.\n- Composition rules (Card\u002FDialog\u002FTabs\u002Fetc.) and component install belong to the **`shadcn` skill** — defer to it for step 5.\n\n> Re-read the theme CSS file before editing; its token blocks are the source of truth and may differ from any assumptions.\n\n## Workflow\n\n### 1. Collect the input\n\nGet the DESIGN.md as a file path, pasted text, or URL. If a URL, fetch the raw markdown (e.g. WebFetch). Confirm it has `---` front matter; if it's prose-only, extract what tokens you can and note the gaps.\n\n### 2. Parse\n\n- **Front matter** (between the `---` fences): `name`, `colors`, `typography`, `rounded`, `spacing`, `components`.\n- **Body** (`##` sections, canonical order): Overview \u002F Colors \u002F Typography \u002F Layout \u002F Elevation & Depth \u002F Shapes \u002F Components \u002F Do's and Don'ts. Section aliases exist (Overview≡\"Brand & Style\", Layout≡\"Layout & Spacing\", Elevation≡\"Elevation & Depth\").\n- Resolve token references `{path.to.token}` (e.g. `{colors.primary}`, `{rounded.md}`) to their values before mapping.\n\n### 3. Map tokens → shadcn (the core step)\n\nFollow [rules\u002Ftoken-mapping.md](rules\u002Ftoken-mapping.md) exactly:\n\n- Color tokens → shadcn semantic variables (with foreground pairs).\n- `rounded.md`\u002F`DEFAULT` → `--radius`.\n- Detect light vs dark from the background's lightness; fill the matching block, derive the opposite block (flag it for review).\n- Normalize every color to the theme file's existing convention (`oklch()`, HSL channels, or raw) — match what's already there; keep the original value in a trailing comment.\n\n### 4. Apply to the theme CSS file\n\nEdit **only** the variable lines inside `:root` and `.dark`. **Preserve** everything else: `@import`s, fonts, `@theme {}` (including any `--color-* → var(--*)` aliases and the `--radius-*` calc scale), and `@layer base {}`.\n\n- Use targeted `Edit` calls per variable block — never overwrite the whole file.\n- Present a concise summary of the changes (old → new per token) before\u002Fwith the edit.\n- Unmapped DESIGN.md tokens: keep them as extra custom vars with a comment, or report them — do not silently drop.\n\n### 5. Component & layout guidance\n\nSummarize the prose (Overview, Layout, Elevation & Depth, Shapes, Components, Do's and Don'ts) into concrete rules for any UI built next — e.g. \"one primary action per screen\", radius\u002Felevation conventions, component variants. Then hand off actual component selection \u002F install \u002F composition to the **`shadcn` skill**.\n\n## Guardrails\n\n- Never overwrite the theme CSS file wholesale — edit token lines only; keep imports\u002Ffonts\u002F`@theme`\u002F`@layer base` intact.\n- Show the token diff before applying so the user can sanity-check.\n- Color conversions (to `oklch()`\u002FHSL) are approximations — recommend a visual check; do not claim exact color fidelity.\n- This skill maps tokens and surfaces guidance; it does not install components (that's the `shadcn` skill) and does not add dependencies.\n- After editing, the user must rebuild\u002Frestart the dev server to see changes — use the project's own build command (e.g. `npm run build`\u002F`dev`, `pnpm`, `bun`, or `vendor\u002Fbin\u002Fsail …` for Laravel Sail setups). Check `package.json` scripts if unsure.\n","# DESIGN.md → shadcn\u002Fui\n\nTake an external **DESIGN.md** (the Google Labs design-token format, version `alpha`, Apache-2.0) and apply it to the project's shadcn\u002Fui theme.\n\n## What this skill is for\n\nThe DESIGN.md format pairs machine-readable YAML front matter (design tokens) with markdown prose (rationale + guidance). It uses a **Material-3-style token namespace** (`primary`, `secondary`, `tertiary`, `neutral`, `surface`, `on-surface`, `surface-container-*`, `on-primary`, …) that does **not** map 1:1 to shadcn's fixed semantic tokens.\n\nThe official `design.md export --format css-tailwind` emits `--color-primary` etc. — single-mode, no foreground pairs — which is **not** usable by shadcn. This skill provides the missing mapping layer: DESIGN.md tokens → shadcn `:root` \u002F `.dark` CSS variables, plus prose → component guidance.\n\n- **Direction:** inbound only (external DESIGN.md → the project). Do not generate a DESIGN.md from the project.\n- **Dependencies:** none. No `@google\u002Fdesign.md` CLI, no package installs. Pure parsing + the mapping table in [rules\u002Ftoken-mapping.md](rules\u002Ftoken-mapping.md).\n\n## Project target (locate, then verify before editing)\n\nFirst find the project's shadcn theme CSS file and config — don't assume a path:\n\n- **Theme CSS file:** the file holding shadcn tokens as CSS variables in `:root` (light) and `.dark`. Common locations: `app\u002Fglobals.css`, `src\u002Findex.css`, `src\u002Fapp.css`, `resources\u002Fcss\u002Fapp.css`, `styles\u002Fglobals.css`. Confirm by grepping for `--background`, `--primary`, or `--radius`.\n- **`components.json`** (repo root): read `style`, `baseColor`, `cssVariables`, `tailwind.css` (points to the theme file), and the `aliases`. Note whether tokens are HSL\u002F`oklch()`\u002Fraw and match that convention.\n- Composition rules (Card\u002FDialog\u002FTabs\u002Fetc.) and component install belong to the **`shadcn` skill** — defer to it for step 5.\n\n> Re-read the theme CSS file before editing; its token blocks are the source of truth and may differ from any assumptions.\n\n## Workflow\n\n### 1. Collect the input\n\nGet the DESIGN.md as a file path, pasted text, or URL. If a URL, fetch the raw markdown (e.g. WebFetch). Confirm it has `---` front matter; if it's prose-only, extract what tokens you can and note the gaps.\n\n### 2. Parse\n\n- **Front matter** (between the `---` fences): `name`, `colors`, `typography`, `rounded`, `spacing`, `components`.\n- **Body** (`##` sections, canonical order): Overview \u002F Colors \u002F Typography \u002F Layout \u002F Elevation & Depth \u002F Shapes \u002F Components \u002F Do's and Don'ts. Section aliases exist (Overview≡\"Brand & Style\", Layout≡\"Layout & Spacing\", Elevation≡\"Elevation & Depth\").\n- Resolve token references `{path.to.token}` (e.g. `{colors.primary}`, `{rounded.md}`) to their values before mapping.\n\n### 3. Map tokens → shadcn (the core step)\n\nFollow [rules\u002Ftoken-mapping.md](rules\u002Ftoken-mapping.md) exactly:\n\n- Color tokens → shadcn semantic variables (with foreground pairs).\n- `rounded.md`\u002F`DEFAULT` → `--radius`.\n- Detect light vs dark from the background's lightness; fill the matching block, derive the opposite block (flag it for review).\n- Normalize every color to the theme file's existing convention (`oklch()`, HSL channels, or raw) — match what's already there; keep the original value in a trailing comment.\n\n### 4. Apply to the theme CSS file\n\nEdit **only** the variable lines inside `:root` and `.dark`. **Preserve** everything else: `@import`s, fonts, `@theme {}` (including any `--color-* → var(--*)` aliases and the `--radius-*` calc scale), and `@layer base {}`.\n\n- Use targeted `Edit` calls per variable block — never overwrite the whole file.\n- Present a concise summary of the changes (old → new per token) before\u002Fwith the edit.\n- Unmapped DESIGN.md tokens: keep them as extra custom vars with a comment, or report them — do not silently drop.\n\n### 5. Component & layout guidance\n\nSummarize the prose (Overview, Layout, Elevation & Depth, Shapes, Components, Do's and Don'ts) into concrete rules for any UI built next — e.g. \"one primary action per screen\", radius\u002Felevation conventions, component variants. Then hand off actual component selection \u002F install \u002F composition to the **`shadcn` skill**.\n\n## Guardrails\n\n- Never overwrite the theme CSS file wholesale — edit token lines only; keep imports\u002Ffonts\u002F`@theme`\u002F`@layer base` intact.\n- Show the token diff before applying so the user can sanity-check.\n- Color conversions (to `oklch()`\u002FHSL) are approximations — recommend a visual check; do not claim exact color fidelity.\n- This skill maps tokens and surfaces guidance; it does not install components (that's the `shadcn` skill) and does not add dependencies.\n- After editing, the user must rebuild\u002Frestart the dev server to see changes — use the project's own build command (e.g. `npm run build`\u002F`dev`, `pnpm`, `bun`, or `vendor\u002Fbin\u002Fsail …` for Laravel Sail setups). Check `package.json` scripts if unsure.\n",{"name":5,"metadata":57,"description":7},{"email":58,"author":59,"version":60},"initred@dou.so","initred","1.0.0","main","ee55538fc8b60bb1595f860f18cbd7baba1925aa","skills\u002Fdesign-md-to-shadcn",0,"https:\u002F\u002Fgithub.com\u002Fdouinc\u002Fagent-skills","https:\u002F\u002Fgithub.com\u002Fdouinc","https:\u002F\u002Fdou.so","A clinical intelligence company","2026-11-12 10:02:01",{"source":8,"skillName":5,"commands":71,"prompt":81,"zipAvailable":82},[72,75,78],{"tool":73,"command":74},"npx","npx skills add douinc\u002Fagent-skills --skill design-md-to-shadcn",{"tool":76,"command":77},"bunx","bunx skills add douinc\u002Fagent-skills --skill design-md-to-shadcn",{"tool":79,"command":80},"pnpm","pnpm dlx skills add douinc\u002Fagent-skills --skill design-md-to-shadcn","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdouinc\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdesign-md-to-shadcn\u002FSKILL.md",true,[84],{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"rules\u002Ftoken-mapping.md","REFERENCE","参考文档",5536,"https:\u002F\u002Fgithub.com\u002Fdouinc\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdesign-md-to-shadcn\u002Frules\u002Ftoken-mapping.md",[91,105,138,152,181,197],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":98,"publishedAt":52},"01M6PDKC7XDA3NYF969T945D7S","template-skill","Replace with description of the skill and when the agent should use it.","https:\u002F\u002Fgithub.com\u002Fdouinc\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftemplate\u002FSKILL.md",[97],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[99,100,101,102,103,104],"template","template skill","it","use","name","with",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":119,"publishedAt":52},"01M6PDK6MNC6EMGA8W7KD7NJQX","writing-project-readme","Use when explicitly invoked to write or fully rewrite a project README that must cover tech stack, architecture, features, and service description in a single document — readable by non-engineers (PM, design, ops, domain experts) as well as developers. Triggers on requests like \"write the README\", \"redo README.md based on the whole project\", \"make a comprehensive README everyone can understand\". Skip for one-section edits, badge tweaks, or generating a CHANGELOG.","https:\u002F\u002Fgithub.com\u002Fdouinc\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-project-readme\u002FSKILL.md",[111,114,115,116],{"categoryNo":112,"categoryName":113,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},{"categoryNo":117,"categoryName":118,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000036","内容创作者",[120,121,122,123,42,124,125,126,127,128,129,130,131,132,133,134,135,136,137,35],"README","writing project readme","project readme","writing","cover","for","tech","domain","as","make","alpha","write","features","experts","changelog","stack","architecture","pm",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":147,"publishedAt":52},"01M6PDK2S8KXK1NDM22C9FKE49","ux-writing-korean","한국어로 UI\u002FUX 문구를 작성하거나 검수할 때 사용합니다. 해요체, 능동형, 긍정형, 캐주얼 경어, 명사 조합 회피 등 5가지 핵심 원칙과 예외 규칙을 적용합니다.","https:\u002F\u002Fgithub.com\u002Fdouinc\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fux-writing-korean\u002FSKILL.md",[144,145,146],{"categoryNo":112,"categoryName":113,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},{"categoryNo":117,"categoryName":118,"taxonomyType":29,"taxonomyTypeDesc":30},[148,123,149,150,151,47],"ux writing","ux","korean","ux writing korean",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":162,"publishedAt":52},"01M6PDJXK3DVWFR0420XV79HZ6","token-audit","Audit a Claude Code or Codex CLI project for token waste and fix it with the user's approval. Use whenever the user wants to check, reduce, or optimize token usage, context bloat, or API\u002Fsubscription costs of an agent project — phrases like \"토큰 점검\", \"토큰 낭비 찾아줘\", \"토큰 최적화\", \"컨텍스트 최적화\", \"Claude Code 비용 줄여줘\", \"API 비용이 너무 나와\", \"audit token efficiency\", \"check my CLAUDE.md\u002FAGENTS.md\u002FMCP setup\". Also trigger when the user complains that sessions hit context limits too fast, that costs jumped unexpectedly, or asks whether their project setup is token-efficient — even if they don't say the word \"token\".","https:\u002F\u002Fgithub.com\u002Fdouinc\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftoken-audit\u002FSKILL.md",[158,159],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":160,"categoryName":161,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000030","开发工程师",[163,41,164,165,166,167,168,169,170,171,172,173,174,175,176,177,178,179,42,180],"audit","token audit","token efficiency","mcp setup","usage","reduce","bloat","my","limits","cli","optimize","efficiency","api","code","context","MCP","fix","codex cli",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":187,"publishedAt":52},"01M6PDJR1Y9BAM48RDKRQHK5MQ","release-showcase","정식 릴리스의 변경을 이전·이후 스크린샷, 클릭 흐름 녹화 영상, 비교·단계·탭·흐름도 같은 HTML 컴포넌트로 보여 주는 파일 하나짜리 릴리스 문서를 만든다. 텍스트뿐인 릴리스 노트로는 어떤 UX가 바뀌었고 새 기능을 어떻게 쓰는지 감이 안 올 때 쓴다. '릴리스 노트 문서 만들어 줘', '릴리스 쇼케이스', '이번 배포 변경사항 정리해서 공유', '릴리즈 노트 HTML', '변경사항을 화면으로 보여 주는 문서', '업데이트 소개 페이지', 'what's new 페이지', 'release notes with screenshots', 'changelog page', '배포 공지 자료'처럼 버전 태그 사이의 변경을 팀·고객에게 시각적으로 알릴 때 반드시 사용한다. git 태그로 릴리스하는 저장소라면 웹·데스크톱·모바일 어느 앱이든 쓴다. 커밋 목록만 필요한 CHANGELOG.md 갱신, 릴리스 태그·배포 자체, 마케팅 영상 제작에는 쓰지 않는다.","https:\u002F\u002Fgithub.com\u002Fdouinc\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frelease-showcase\u002FSKILL.md",[],[188,189,190,104,191,192,193,194,195,196,134],"release","showcase","release showcase","release notes","page","notes","screenshots","html","git",{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":201,"categories":202,"keywords":205,"publishedAt":52},"01M6PDJJEQMBWWXW4TPXYNNV38","public-sector-rfp-authoring","Use when drafting or revising Korean government or local-government bid notices, requests for proposals, statements of work, or public-sector service\u002Fproject specifications from the ordering agency's perspective.","https:\u002F\u002Fgithub.com\u002Fdouinc\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-sector-rfp-authoring\u002FSKILL.md",[203,204],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[206,207,208,209,210,211,212,213,214,215,216,102,125,217,218,219,42,150],"authoring","rfp","public","public sector rfp authoring","specifications","hermes agent","hermes","perspective","service","agency","requests","proposals","work","local"]