TG-SignPulse is an AI Vibe Coding learning project created to explore and practice the integration of the following technology stacks:
- Frontend/backend separation architecture (Vue 3 + FastAPI)
- Modern Python async programming patterns
- AI/LLM API integration (OpenAI-compatible interface calls)
- Task scheduling system design (APScheduler)
- Web authentication (JWT + TOTP 2FA)
This project was built as a hands-on exercise during the author's exploration of AI-assisted programming (Vibe Coding). It demonstrates how AI coding tools can be applied in a full-stack project. The codebase was primarily generated with AI assistance, serving as a showcase of AI-driven development workflows.
🚫 This project is discontinued and will not receive further updates.
- No pre-built images or distributions of any kind are provided
- No new Issues or Pull Requests will be accepted
- The code is available solely for technical learning reference
Technologies used in this project, for learning reference:
| Layer | Technology |
|---|---|
| Frontend | Vue 3, Vue Router, Pinia, Tailwind CSS 4, Vite |
| Backend | FastAPI, Uvicorn, SQLAlchemy, SQLite, APScheduler |
| Auth | JWT, TOTP 2FA, bcrypt |
| AI Integration | OpenAI SDK (API call examples) |
| Third-party API | Pyrogram (Telegram MTProto protocol study) |
This project can serve as a reference for:
- Full-stack project structure — Organizing a frontend/backend separated application
- Async Python — Practical use of FastAPI + asyncio
- Task scheduling — Integrating APScheduler in a web application
- AI API calls — Wrapping and using OpenAI-compatible interfaces
- Authentication system — Implementing JWT + 2FA
- State management — Using Pinia with Vue 3
- This project is intended solely for AI programming technique learning and exchange; it does not encourage or support any form of automation abuse
- The author is not responsible for any consequences arising from the use of this code
- No technical support or deployment services are provided
- Third-party API calls in the code are included only as technical examples; users must comply with the relevant terms of service on their own
The Telegram protocol interaction portion of this project references tg-signer by amchii.