Ray Studio
Contact
Ray Studio

Uses

Tools, systems, and rituals I trust for writing, designing, coding, and shipping.

Updated Jun 202612 tools5 workflows

Filter tools

12 / 12 tools
Next.jsTypeScriptMDXVercelFigmaRaycastCursor

Current stack

Core technologies and platforms I build with right now.
Code⌘ N

Next.js

React framework

The default surface for fast editorial pages, MDX routes, and production deploys.App Router / Metadata / Static routes
Code⌘ T

TypeScript

Language

Keeps content models, component props, and route contracts legible as the studio grows.Strict enough for structure, light enough for iteration
Writing⌘ M

MDX

Content format

Turns essays, project notes, and technical examples into versioned source files.Portable writing with code-native components
Automation⌘ V

Vercel

Deployment

Production previews, deploy history, and a tight feedback loop from commit to public URL.Small releases, traceable deployments
Design⌘ F

Figma

Interface design

Used for visual direction, component thinking, and sharpening page-level intent.Design before density
Automation⌘ R

Raycast

Launcher

The command layer for quicklinks, scripts, clipboard, windows, and project jumps.Keyboard-first access to repeated moves
Code⌘ C

Cursor

AI code editor

A focused place for code edits, refactors, and local reasoning over the repo.Agentic coding with local context
Automation⌘ L

Linear

Issue tracking

A model for calm planning, clear status, and lightweight operational surfaces.Status without dashboard noise
Code⌘ G

GitHub

Source control

The trace layer for commits, issues, milestones, and release decisions.Every meaningful change gets provenance
Writing⌘ D

Feishu

Knowledge cloud

Cloud reading, comments, project maps, and phase reviews synced from local Markdown.Local source of truth, cloud collaboration layer
Automation⌘ P

Playwright

Browser QA

Used for rendered checks, screenshots, interaction proof, and responsive validation.Trust the browser, not just the build
Design⌘ O

OpenAI

Concept partner

Supports visual concepting, product reasoning, writing synthesis, and implementation reviews.Use AI to clarify taste, not to hide weak structure

Workspace rhythm

A day in four movements. Deep work first, everything else around it.

00中文复盘

把阶段判断、页面边界、验证结果和下一步写成中文，先进入本地 Markdown，再同步飞书。

⌘ 0
01Deep work

Write, design, or code before messages reshape the day.

⌘ 1
02Sync and respond

Review comments, GitHub issues, Feishu notes, and small decisions.

⌘ 2
03Build and iterate

Ship focused increments with visible QA and deploy traces.

⌘ 3
04Capture and close

Update the project map, record the next slice, and leave clean trails.

⌘ 4

Protect the morning. Design the afternoon. Close with trace.

Publishing pipeline

From idea to production, every step leaves a useful trail.

  1. 1IdeaKnowledge / Feishu
  2. 2Draft中文复盘 / MDX
  3. 3BuildNext.js / TypeScript
  4. 4ReviewPlaywright / GitHub
  5. 5DeployVercel / Trace

Automation shelf

Small repeatable moves that remove friction without adding theatre.

Code snippetsIssue triageDeploy checksDoc sync