Complete architecture reference for the A3 insurance platform — file locations, data flow, conventions, microservice map, and fullstack patterns
日本語の概要は準備中です。原文の説明を表示しています。
Deploy and operate the vehicle insurance data analysis platform. Use when user asks about local development setup, production deployment, server configuration, build process, service management, or troubleshooting deployment issues. Focuses on the project's actual simple deployment model using start_server.sh, not complex enterprise setups.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
You are assisting with deploying and operating the vehicle insurance data analysis platform. This project uses a simple deployment model suitable for internal teams and small-scale production.
Activate this skill when the user needs help with:
start_server.sh)Current Approach: Simple, single-server deployment
start_server.shThis is appropriate for:
Guide the user to verify:
# Check Python (3.11+ required)
python3 --version
# Check Node.js (18+ recommended)
node -v
# Check if in correct directory
pwd # Should show /path/to/签单日报dayreport
# Start backend with the provided script
./start_server.sh
# Output:
# ========================================
# 每日签单平台趋势分析系统
# ========================================
# [1/3] 检查Python环境...
# [2/3] 检查依赖包...
# [3/3] 启动API服务器...
# 服务器地址: http://localhost:5000
What this script does:
/static/index.html# Terminal 1: Start backend
cd backend
python3 api_server.py
# Terminal 2: Start frontend dev server (if doing frontend dev)
cd frontend
npm install # First time only
npm run dev # Starts Vite on http://localhost:5173
Install dependencies:
# From project root
pip3 install -r requirements.txt
# Requirements (from requirements.txt):
# - flask==3.0.0
# - flask-cors==4.0.0
# - numpy>=2.2,<3
# - pandas>=2.2.3,<3
# - openpyxl==3.1.2
Optional: Use virtual environment:
# Create venv (recommended for clean dependency management)
python3 -m venv .venv
# Activate
source .venv/bin/activate # macOS/Linux
# .venv\Scripts\activate # Windows
# Install deps
pip install -r requirements.txt
Only needed if user wants to modify Vue components:
cd frontend
# Install dependencies
npm install
# Available commands
npm run dev # Start dev server (http://localhost:5173)
npm run build # Build for production (outputs to dist/)
npm run preview # Preview production build
npm run lint # Run ESLint
cd frontend
# Production build
npm run build
# Output:
# vite v5.0.10 building for production...
# ✓ 104 modules transformed.
# dist/index.html 0.48 kB
# dist/assets/index-xxx.js 80.68 kB │ gzip: 31.98 kB
# dist/assets/index-xxx.css 14.05 kB │ gzip: 2.86 kB
Build artifacts: frontend/dist/
index.html - Entry pointassets/ - Bundled JS/CSS with content hashesSimple deployment (current method):
# 1. Copy entire project to server
scp -r /path/to/签单日报dayreport user@server:/opt/dayreport/
# 2. SSH to server
ssh user@server
# 3. Install Python deps
cd /opt/dayreport
pip3 install -r requirements.txt
# 4. Start service
./start_server.sh
# Or run in background
nohup ./start_server.sh > app.log 2>&1 &
# If using start_server.sh (default):
http://server-ip:5000/static/index.html
# If using frontend dev server:
http://server-ip:5173
# Check backend (port 5000)
lsof -i :5000
# Or
ps aux | grep api_server
# Check frontend dev server (port 5173)
lsof -i :5173
# Stop backend
pkill -f api_server
# Stop frontend dev server
# (Ctrl+C in terminal, or)
pkill -f vite
# Restart backend
cd backend && python3 api_server.py &
# Restart frontend
cd frontend && npm run dev &
# Run backend in background
nohup python3 backend/api_server.py > backend.log 2>&1 &
# Get process ID
echo $! # Save this PID
# Stop later
kill <PID>
Location: backend/backend.log
# View real-time logs
tail -f backend/backend.log
# View last 50 lines
tail -n 50 backend/backend.log
# Search for errors
grep -i "error" backend/backend.log
# View logs with timestamps
tail -f backend/backend.log | while read line; do echo "$(date): $line"; done
Browser console: Open DevTools (F12) → Console tab
Build logs: Terminal output during npm run build
Symptom:
OSError: [Errno 48] Address already in use
Solution:
# Find and kill process using port 5000
lsof -i :5000
kill -9 <PID>
# Or change port in api_server.py
# app.run(host='0.0.0.0', port=5001) # Use different port
Symptom:
ModuleNotFoundError: No module named 'flask'
Solution:
# Verify Python environment
which python3
python3 -m pip list
# Reinstall dependencies
pip3 install -r requirements.txt
# If still failing, check if using correct Python
python3 -c "import flask; print(flask.__version__)"
Symptom:
-bash: ./start_server.sh: Permission denied
Solution:
# Add execute permission
chmod +x start_server.sh
# Then run
./start_server.sh
Symptom:
FileNotFoundError: 车险清单_2025年10-11月_合并.csv not found
Solution:
# Check if file exists
ls -la *.csv
# Check data directory
ls -la data/
# Verify file paths in data_processor.py match actual locations
Symptom:
npm ERR! code ENOENT
Solution:
# Clean install
rm -rf node_modules package-lock.json
npm install
# If disk space issue
df -h # Check available space
# If memory issue
NODE_OPTIONS=--max-old-space-size=4096 npm run build
# CPU and memory (macOS)
top -o CPU
# Specific process
ps aux | grep python3 | grep api_server
# Disk usage
df -h
du -sh /path/to/签单日报dayreport/*
# Test API response time
time curl http://localhost:5000/api/latest-date
# Multiple requests benchmark
for i in {1..10}; do
time curl -s http://localhost:5000/api/kpi?period=day > /dev/null
done
Important files to backup:
# 1. Merged CSV data
车险清单_2025年10-11月_合并.csv
# 2. Staff mapping
业务员机构团队归属.json
# 3. Raw Excel files (optional)
data/*.xlsx
# Backup command
tar -czf backup-$(date +%Y%m%d).tar.gz \
车险清单_2025年10-11月_合并.csv \
业务员机构团队归属.json \
data/
# Restore
tar -xzf backup-20250108.tar.gz
Note: These are NOT currently implemented but can be added later:
# /etc/nginx/sites-available/dayreport
server {
listen 80;
server_name your-domain.com;
location / {
proxy_pass http://127.0.0.1:5000;
proxy_set_header Host $host;
}
}
# /etc/systemd/system/dayreport.service
[Unit]
Description=Dayreport API Service
[Service]
Type=simple
WorkingDirectory=/opt/dayreport
ExecStart=/usr/bin/python3 backend/api_server.py
Restart=always
[Install]
WantedBy=multi-user.target
Enable:
sudo systemctl daemon-reload
sudo systemctl enable dayreport
sudo systemctl start dayreport
For detailed advanced deployment, refer to ADVANCED_DEPLOYMENT.md.
Create .env file (if needed for configuration):
# .env
FLASK_ENV=production
FLASK_DEBUG=False
DATA_DIR=/opt/dayreport/data
PORT=5000
Load in Python:
# backend/api_server.py
import os
from dotenv import load_dotenv
load_dotenv()
PORT = int(os.getenv('PORT', 5000))
Before deploying to production:
npm run build)pip install -r requirements.txt)curl localhost:5000/api/latest-date)# Start
./start_server.sh
# Stop
pkill -f api_server
# Logs
tail -f backend/backend.log
# Build frontend
cd frontend && npm run build
# Check status
lsof -i :5000
ps aux | grep api_server
项目/
├── start_server.sh # Main startup script
├── requirements.txt # Python dependencies
├── backend/
│ ├── api_server.py # Flask app (runs on :5000)
│ ├── data_processor.py # Pandas logic
│ └── backend.log # Runtime logs
├── frontend/
│ ├── package.json # Node dependencies
│ └── dist/ # Built artifacts (after npm run build)
├── data/ # Excel source files
└── *.csv # Processed CSV data
This skill covers the actual deployment model used by this project:
start_server.shKey principle: Start simple, scale when needed. The current deployment is appropriate for the project's scope.
For enterprise-grade deployment patterns (Docker, K8s, load balancing), refer to advanced guides only if project requirements change.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Complete architecture reference for the A3 insurance platform — file locations, data flow, conventions, microservice map, and fullstack patterns
日本語の概要は準備中です。原文の説明を表示しています。
Drafts U.S. commercial real estate access and indemnity (right-of-entry) agreements for pre-closing due diligence. Covers license grants, non-invasive vs invasive testing gates, insurance/endorsement requirements, indemnity with discovery carve-outs, restoration and lien remedies, confidentiality, and anti-indemnity guardrails. Trigger: access agreement, right of entry, due diligence access, Phase I/II, invasive testing, pre-PSA site inspection.
日本語の概要は準備中です。原文の説明を表示しています。
当用户需要对意外险投保问卷进行专业、结构化的核保审查,提取职业类别、工作环境、作业内容、危险活动参与情况、交通出行习惯、特殊工作暴露及其他可能影响意外险承保判断的高风险信息,并生成适合意外险核保、补问流转和风险分层处理的结构化分析结果时使用本 skill。
日本語の概要は準備中です。原文の説明を表示しています。
Inspect, schema, and fill true AcroForm PDFs using sciClaw's pdf_form_inspect, pdf_form_schema, and pdf_form_fill tools. Use when: (1) checking whether a PDF is a real fillable AcroForm, (2) listing form field names, types, and choices, (3) filling a supported form from structured values, (4) preparing reviewable insurance, legal, administrative, or clinical form drafts, (5) reporting skipped fields or unused input keys after a fill. Do not use for scanned PDFs, OCR tasks, or XFA-only forms.
日本語の概要は準備中です。原文の説明を表示しています。
Guide actuarial analysis for insurance pricing. TRIGGERS - Use when user needs help with actuarial-analysis related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes actuarial modeling systems for loss reserving accuracy, premium pricing methodology, mortality/morbidity tables, stochastic modeling, and capital adequacy per SOA and Solvency II standards. USE THIS SKILL WHEN: - You need to review or audit actuarial models (reserving, pricing, capital) - Someone asks about loss triangle analysis or reserve adequacy - You are evaluating IBNR calculations, chain ladder methods, or Bornhuetter-Ferguson - A project involves insurance pricing, GLM rating models, or ratemaking - You need to assess Solvency II SCR calculations or RBC compliance - Someone mentions actuarial opinions, ASOP compliance, or SOA standards - You are reviewing stochastic models, ESG configurations, or DFA frameworks - A codebase uses actuarial libraries (chainladder, lifetables, ChainLadder R package) TRIGGER PHRASES: "actuarial", "loss reserving", "IBNR", "chain ladder", "premium pricing", "mortality table", "Solvency II", "capital adequacy", "ratemaking", "GLM pricing", "risk-based capital", "reserve analysis", "actuarial opinion"
日本語の概要は準備中です。原文の説明を表示しています。