القائمة
Automatically helps the user configure their local environment by running the setup wizard to generate the required .env file and prompting them to find missing API credentials.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
How to add or update content on this site — work entries, blog posts, talks, pages, static assets, or a whole new content type. The CMS is the filesystem.
How Ryan designs. Use before changing style.css, page layouts in build.mjs, or adding any visual element to the site.
How Ryan writes. Use whenever drafting or editing any prose for this site — work case studies, blog posts, page copy, talk abstracts, even link summaries.
Audit publishable portfolio copy, content completeness, claims, links, canonicals, redirects, images, social metadata, accessibility, and rendered presentation. Use for every public content addition or meaningful edit before it is considered ready for review or publication.
Use this skill when needing to convert street addresses into precise geographic coordinates (geocoding) or translating coordinates back into human-readable addresses (reverse geocoding). Developers can refine results using viewports, regional restrictions, or retrieve detailed location information for addresses, coordinates, or Google Place IDs, including building outlines and entrances.
Use for Google Maps Platform Environment APIs work, including Air Quality API, Pollen API, Solar API, Weather API, environmental heatmap tiles, current/forecast/history requests, Maps JavaScript API tile overlays, key security, quotas, caching, attribution, health recommendation UX, and migrations from PurpleAir or other environmental data sources.
| name | setup-local-environment |
| description | Automatically helps the user configure their local environment by running the setup wizard to generate the required .env file and prompting them to find missing API credentials. |
find . -name ".env" to see if a root .env file exists. If it exists, ask the user if they want to overwrite it before proceeding.stdin prompts) block automated test agents, do NOT run npm run setup in the background via run_command.run_command tool to read the .env.template file: cat .env.template.npm run setup or edit the ignored root .env locally.GEMINI_API_KEY, STRAVA_CLIENT_SECRET, GMP_SERVER_API_KEY, tokens, and passwords as server-only.npm run build && npm start) if it was already running.npm run build to ensure Vite successfully detects and injects the VITE_ prefixed variables without errors..env file was successfully written and all applications are ready for local testing..env.template, scripts/setup.mjs, and this skill file to capture the new key.