返回提示词目录第 22 页

核心价值 :这是一个基于 Astro + Svelt

核心价值 :这是一个基于 Astro + Svelt:核心价值 :这是一个基于 Astro + Svelte + Tailwind CSS 构建的极简个人博客,以"安静、克制、有结构"为设计理念,提供沉浸式的阅读体验。 适用场景 :适合作为个人技术博客、创作笔记、训练日志的发布平

完整提示词

Install this skill: https://github.com/TencentEdgeOne/edgeone-pages-skills, then deploy to EdgeOne Pages.

## WorkBuddy Competition Prompt — Construction-Grade Self-Contained Personal Blog for Senguk

You are building a **brand-new personal blog website from scratch**.

This prompt is intentionally **self-contained** and must be treated as the **only execution source**.

Do **not** assume access to:
- any previous repository
- any hidden project files
- any local `src/...` or `public/...` assets
- any earlier conversation memory outside this prompt
- any prebuilt theme, starter, or blog template that defines the final structure for you

If something is not provided, resolve it according to the fallback and acceptance rules in this prompt instead of asking to inspect an old codebase.

If there is any conflict between:
- visual experimentation and implementation stability → choose **implementation stability**
- decoration and page completeness → choose **page completeness**
- artistic mood and reading usability → choose **reading usability**
- optional enhancements and required pages → choose **required pages**

The result must be suitable for **WorkBuddy competition delivery**, **EdgeOne Pages deployment**, and **stable reproduction by a new CodeBuddy conversation** that only receives some initial images.

## 1. Core Mission

Build a complete, production-quality, multi-page personal blog for **Senguk's blog**.

This website must feel:
- restrained
- premium
- soft and luminous
- airy and editorial
- emotionally calm
- elegant instead of cute
- anime-inspired only in atmosphere, never in literal character focus

This is **not**:
- a landing page
- a one-screen visual demo
- a portfolio-only shell
- a mascot-centered anime site
- a generic SaaS template

It must be a real personal publication system with enough structure for long-term writing, archives, gallery browsing, project documentation, diary fragments, and real reader interaction.

## 2. Fixed Brand Inputs

Use these inputs **exactly**. Do not paraphrase, localize, rename, or reinterpret them.

- Chinese site name: **苏不不不酥的小站**
- English site name: **Senguk's blog**
- Slogan: **A seed of resolve planted in the heart, Endurance becomes a required art.**
- Bio: **心中埋下争气的种子,忍耐便是人生的必修课**
- Home hero title: **Like splitting bamboo**

These must remain fixed in the final result.

## 3. Site Personality and Tone

The emotional identity must communicate:
- restraint
- endurance
- softness
- quiet inner strength
- patience
- emotional maturity
- gentle reflection

The writing tone across the interface should feel:
- calm
- thoughtful
- warm but not childish
- poetic but not pretentious
- refined but not commercial

Avoid copy that feels:
- cute for the sake of cuteness
- startup-like
- over-marketed
- loud or clickbait-driven
- fan-service heavy
- cold and robotic

## 4. Audience and Use Cases

Build the site for readers who enjoy:
- long-form writing
- personal reflection
- calm visual environments
- project and skill documentation
- timeline-based life records
- image-led album browsing
- short diary fragments

Primary use cases:
- browsing recent writing from the homepage
- reading full articles with strong typography, rendered Markdown, and TOC support
- navigating older content through archive and search
- browsing links, albums, projects, skills, and timeline records
- experiencing clearly differentiated desktop and mobile layouts rather than one compressed shared layout
- leaving comments on articles through a real usable comment provider

## 5. Explicit Non-Goals

Do **not** allow the final site to become:
- a character shrine
- a fandom page
- a neon cyberpunk showcase
- a collage-heavy art experiment
- a dashboard-style admin interface
- a visual-only mockup without real page depth

## 6. Required Tech Direction

Use a modern blog-friendly stack that can be deployed, previewed, and verified directly on EdgeOne Pages.

Preferred stack:
- Astro
- Svelte for interactive islands where needed
- Tailwind CSS
- TypeScript
- a soft page-transition system in the spirit of Swup
- a static-friendly local search solution in the spirit of Pagefind
- a real usable comment solution such as Giscus or Twikoo
- markdown rendering and prose styling that produces a true reading page instead of raw source text

Do not overcomplicate the stack. Choose maintainability, readability, EdgeOne compatibility, and static-friendly performance.

## 7. Required Information Architecture and Routes

The final site must contain these routes or direct equivalents with the same content meaning:

1. `/` — Home
2. `/posts/[slug]/` — Article detail page
3. `/archive/` — Archive page
4. `/about/` — About page
5. `/friends/` — Friends / Links page
6. `/albums/` — Albums / Gallery page
7. `/albums/[id]/` — Album detail page
8. `/projects/` — Projects page
9. `/skills/` — Skills page
10. `/timeline/` — Timeline page
11. `/diary/` — Diary / Micro-journal page
12. search capability — preferably overlay/panel, not necessarily a standalone route
13. comment capability on article pages
14. `/404/` or framework-equivalent custom 404 page

Do not shrink this site into only home + posts + about.

## 8. Explicitly Forbidden Modules

Do **not** include any of the following in the target site:
- Live2D mascot
- Pio companion
- anime / bangumi / watchlist page
- music player
- sakura falling effect
- devices page
- share poster generator
- overly cute mascot decoration
- character-centered home hero
- noisy particles or festival effects
- gamified UI distractions

These are **forbidden target features**, not optional toggles.

## 9. Execution Priority

Follow this order strictly:
1. fixed brand inputs
2. forbidden-module exclusion
3. required routes and page completeness
4. global layout system
5. reusable component system
6. page-by-page blueprints
7. search and real comments capability
8. asset mapping and fallback generation
9. motion polish and page-level interaction quality
10. EdgeOne deployment readiness and acceptance checks

## 10. Remote Asset Protocol

The site may be built in a fresh conversation where the user only provides a small number of remote image URLs.

Use user-provided assets first.
Do not assume local path mirrors.
Do not rewrite the asset strategy around `src/...` or `public/...` references.

### Provided Remote URL Asset Pack (use directly when available)

Map the following roles exactly when the user provides this pack:

- `assets.banner.desktop`
  - `https://edgeone.senguk.top/public/PC/1.webp`
  - `https://edgeone.senguk.top/public/PC/2.webp`
  - `https://edgeone.senguk.top/public/PC/3.webp`
  - `https://edgeone.senguk.top/public/PC/4.webp`
  - `https://edgeone.senguk.top/public/PC/5.webp`
  - `https://edgeone.senguk.top/public/PC/6.webp`
- `assets.banner.mobile`
  - `https://edgeone.senguk.top/public/mobile/1.webp`
  - `https://edgeone.senguk.top/public/mobile/2.webp`
  - `https://edgeone.senguk.top/public/mobile/3.webp`
  - `https://edgeone.senguk.top/public/mobile/4.webp`
  - `https://edgeone.senguk.top/public/mobile/5.webp`
  - `https://edgeone.senguk.top/public/mobile/6.webp`
- `assets.avatar`
  - `https://edgeone.senguk.top/public/avatar.webp`
- `assets.favicon`
  - `https://edgeone.senguk.top/public/favicon.ico`
- `assets.hero.home`
  - `https://edgeone.senguk.top/public/home.png`
- `assets.cover.articleDefault`
  - `https://edgeone.senguk.top/ai-fitness.webp`
- `assets.project.defaultPreview`
  - `https://edgeone.senguk.top/AI-Fitness.jpg`

### Asset usage constraints

- Use remote URLs directly first; do not download and rehost as the default workflow.
- The browser favicon, site icon, and related head metadata must use `assets.favicon` exactly when it is provided.
- Keep desktop and mobile banner pools strictly separated.
- The homepage `hero-overlay` must be implemented as a real rotating carousel rather than a single static hero image.
- Desktop hero slides must come from `assets.banner.desktop[]`; mobile hero slides must come from `assets.banner.mobile[]`; do not mix them.
- `assets.hero.home` may be used only as a single-image fallback when the required banner carousel pool is missing or broken.
- Non-home pages should reuse the same homepage image atmosphere as a subtle ambient layer: prefer the same `assets.banner.desktop[]` / `assets.banner.mobile[]` carousel pools used by the homepage, or `assets.hero.home` only as a fallback, as a blurred, low-opacity, gradient-masked page background behind glass surfaces. Do not let non-home pages fall back to a plain gold/black radial-gradient-only background when banner assets exist.
- The homepage carousel and non-home ambient background must share one synchronized banner index and timing model. If the homepage is currently showing slide `N`, navigating to any non-home page must initially show slide `N` from the corresponding desktop/mobile banner pool and continue rotating to later slides instead of resetting to slide `0` or freezing on a static image.
- Implement the shared carousel state with a static-friendly client mechanism such as `localStorage` plus a timestamp and a custom browser event. Store at least `index` and `updatedAt`, derive the current index from elapsed time, and use one shared interval constant so page navigation does not interrupt the carousel rhythm.
- Keep desktop and mobile banner pools strictly separated while sharing only the numeric slide index; never use desktop URLs on mobile or mobile URLs on desktop just to satisfy synchronization.
- Every hero, card, album, project, and prose image must render inside a ratio-controlled wrapper with bounded height, hidden overflow, and intentional cropping rules rather than exposing raw remote dimensions.
- `assets.avatar` must be used in About page identity sections and any author/profile card.
- `assets.cover.articleDefault` may be used as an SEO, Open Graph, article-detail banner, or explicit fallback-cover seed, but homepage/latest-post cards must not blindly show it for every post that lacks a genuinely adapted cover. If a post has no real post-specific cover and no curated fallback pool, hide the media area or use a neutral placeholder treatment instead of displaying a misleading repeated default image.
- `assets.project.defaultPreview` should be used as the default project preview when a project-specific image is missing, ideally as a muted full-card or bounded-media visual with text-safe overlay treatment rather than an awkward isolated raw image block.

## 11. Fallback Asset Generation Rules

If provided images are missing, broken, insufficient, visually inconsistent, or too low quality, generate replacements according to this rule set.

### Required mood
- scenic
- quiet
- breathable
- low saturation
- soft cinematic light
- emotionally restrained
- elegant rather than commercial
- anime-inspired only in atmosphere, never in literal anime characters

### Preferred subjects
- distant mountains
- lakeside light
- cloudy sky after rain
- soft green summer trees
- city edges at dusk
- window light on a desk
- quiet travel scenes
- calm streets with pale sunlight
- still water, bridges, rail lines, wind, empty paths

### Explicitly avoid
- literal anime characters
- mascot illustrations
- idol imagery
- moe-style decoration
- flashy cyberpunk neon scenes
- nightclub aesthetics
- oversexualized figures
- noisy collage composition
- commercial stock-photo energy

### Missing-asset generation priority
1. home hero / homepage banner set
2. article fallback cover set
3. about-page support image
4. project placeholder set
5. archive / search / gallery / diary / 404 empty-state illustrations
6. subtle section-divider atmosphere images

Only generate the categories that are actually missing.

## 12. Global Design System

### 12.1 Core spatial values

Use these values as **direct implementation targets**, not vague inspiration:

- `--page-width`: `90rem`
- `--sidebar-width`: `17.5rem`
- `--banner-height`: `35vh`
- `--banner-height-home`: `65vh`
- `--content-top-offset-no-banner`: `5.5rem`
- `--radius-card`: `1rem`
- `--radius-small`: `0.75rem`
- `--radius-pill`: `999px`
- `--blur-glass`: `8px`
- `--transition-fast`: `150ms`
- `--transition-medium`: `250ms`
- `--space-section-desktop`: `3rem`
- `--space-section-mobile`: `1.5rem`

### 12.2 Breakpoints

Use these exact responsive breakpoints:
- mobile: under `768px`
- tablet: `768px–1279px`
- desktop: `1280px and above`

Responsive hard rules:
- desktop, tablet, and mobile must not be near-identical compressed versions of the same layout
- desktop may use wider hero media, multi-column composition, side panels, and denser metadata presentation
- tablet must simplify column count and supporting panels without collapsing into the exact mobile arrangement
- mobile must re-stack navigation, hero copy, CTA rows, filters, metadata, and card internals into a touch-first single-column reading flow
- if the desktop and mobile screenshots look almost the same except for scale, the implementation fails this prompt

### 12.3 Typewriter timing

If a typewriter subtitle is used, use:
- type speed: `100ms`
- delete speed: `50ms`
- pause time: `2000ms`

### 12.4 Color system direction

Build a refined light-first palette with calm dark-mode support.

Primary palette direction:
- warm beige
- misty off-white
- pale sage green
- soft dusty pink
- low-saturation brown-gold accents
- deep warm neutrals for text

Use a warm hue direction around **60**.

### 12.5 Recommended semantic CSS variables

Define a semantic token system so the final site remains consistent:

可替换内容

  • [slug]
  • [id]

分类与标签

AI 图片

前往 AI 图片创作